Related
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
I don't know, maybe I've been preaching to deaf ears or something...but...you can re-install the old ROM back, the CWM recovery won't work with the official GB - that much is true - but you will be able to downgrade to an official 2.2.2 (I used the B162) version with the regular update method (at least I was and everything is working just as normal as it used to).
So, irreversible - I don't think so
with the current CWM recovery - it's a no-go
edit: that being said, what works for me, doesn't necessarily work for everyone, so be careful and blame the guy in the mirror -not me, if it doesn't work for you. =)
I think Huawei says wrong here. I flashed 2.3 yesterday. After that, because of the haptic issue I flashed back to official 2.2. Only problem after the 2.2, recovery console had opened. I did factory reset there and phone started without a problem. Then, I had upgraded to 2.3 again. Still haptic don't vibrate. Other than, no problem here. Maybe, I will go back again to 2.2.
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
what 2.2 version is that and you did it after or before rooting?
Have you tried with internal sd? I copied dload folder to internal and started the upgrade process from Storage-Upgrade Firmware. Where did your phone stuck?
Edit: I didn't root my phone. Waiting proper solution. I had used B138.
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Druida69 said:
Well you are lucky then because you are the only one.
Perhaps what is saying in the official intructions that will be impossible to dowgread after this upgrade won't apply to you.
I have try it with at least 8/9 versions of official release and nothing works!!!!
Click to expand...
Click to collapse
Well, like I said, what works for me doesn't necessarily work for you.
Anyway, this is what I did and it worked, maybe it can help others.
0. Copy the original B162 ROM ("dload"-folder which has two files, UPDATE.APP AND UPDATE_CUST.APP) to the root of your SDCARD
1. Update to B162 by holding down +- keys while turning on the phone
2. After the first reboot, it's giving error messages for not being able to mount this and that...just ignore it and...
--> Wipe data / factory reset --> remove battery
3. Update the B162 again --> this time everything should go OK, if so, your phone is back to stock B162 and you're ready to use it or update a custom rom (just install Clockwork recovery like you used to and start from there)
The last point (3) may be unnecessary, but I did so just to make sure everything's ok.
Edit: OK, and I meant b162, not b160...
Druida69 said:
no, I'm using external SD.
now I'm downloading another official release to try to downgrade using another one...
this time is U8800 V100R001C17B162CUSTC17D001
Click to expand...
Click to collapse
For me it also works. I have downgrade without any problem and I use to the b 162 version. Now Ian back to oxygen
Sent from my u8800 using XDA App
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Druida69 said:
yes I made it with this B162.
**** this **** I'm going back to custom rom.
No point of using this official release if future customs will use the libs from this one.
Click to expand...
Click to collapse
And then there's the fact that the official gb is still beta, it's not supposed to work perfectly. But as long as the dev team here stays active, I think that I'm gonna stick with custom roms too.
ho my god.
didn't work.
is always booting into recovery
I am stuck here also (
Nothing worked
I tried clockwork recovery - it doesnt get to. It is just rebooting.
I tried with various dload UPDATE.IMG's (GB Overseas, GB orig chinese,B162,B138) nothing is working - stucked in "Step 1/2 Unpacking" window forever.
Anyone has solution for this ?
Two weeks ago I've flashed the U8800Pro version - real mistake
I've started a topic here:
http://forum.xda-developers.com/showthread.php?t=1327715
katu2006 and on the second page flibblesan gave me a method to start my phone working well.
Post #4, #11 and #13.
Maybe this will help you,too?
sbasil said:
Anyway, this is what I did and it worked, maybe it can help others. (...)
Click to expand...
Click to collapse
You sir are a LEGEND. My phone "lives" again! On CM7 again...
manage to install miui.
several versions now up to the newest one.
I noticed on all of them that it mount the SD card when connected to USB but only shows the system files and not allow writing, copy, cut, etc.
Saying that I dont have permission to change the SD
Druida69 said:
Flashing the official gingerbread in u8800 its irreversivel process, at least for now.
If you flash it you have to keep it as no way of going back.
If you root it using the only available method, bye bye!
Everytime you reboot the endless bootlooping starts and the only way to stop it is formatting data.
Which means everytime you reboot = bye bye all data and apps etc.
I think is something that its major importance and no one is mentioning this!!!!
Click to expand...
Click to collapse
I have just flashed with new U8800V100R001C00B517G001(Beta1.0)(Overseas Normal)(Gingerbread) but after flashing I kept waiting for start my phone. I restasted many times but same, then I format data its worked and when restarted again it goes in same condition any help ?
until flash disk is writable and it is - there will always be way to go back to old versions it just files.. like reinstalling windows on your pc.
Since the new Rom is public I have read all posts about it here. Maybe I had lucky, or simple due it without messing with the files.
Yesterday I made the upgrade to the new rom, directly from the last Oxigen version, without downgrade to 2.2. I simply create the dload folder on SD card, put there de update file, boot with +- Power, and chose upgrade from SD card.
After step 2 I reboot the phone a install step 3 upgrade. Everything as installed fine, no boot loops, nothing...
Also the root method decribed in this forum as work on first time.
24 hours after the upgrade, and some reboots to test, I never se the boot loops, and the phone is working well.
The new ROM, even in beta stage, to me is a great improvement.
Well either you were lucky or me and the majority were unlucky.
But issues only start to happens when rooting.
So that you can see it fried me the 1 USB cable. This cable is only good to charge the battery now....
Also, ****ed the device USB storage MOUNT.
I connect it to the computer and the computer sees it as a CD drive not allowing any changes.
Also when press the button to mount the USB on the device it never gets mounted and gives the messages that the SD can now be removed.
So I have put this issue many times but up to the moment no one even reply to help.
I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
If you have the paid version of the TiBu then you can freeze it with that.
1.ATRIX-in-PT said:
I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Click to expand...
Click to collapse
What's wrong with 4.5.141? I installed it and just rerooted/unlocked/flashed
Hi live4nyy !
Thanks. The file is /system/app/Upgrader.apk ?
Hi ericc191 !
Probably you are right and nothing is "wrong" with 4.5.141 and "no risk, no fun". But it seems, that it includes just some little improvements.
It's not a real system update, so I am not very much in the mood for all this struggle to get my Atrix back to normal after the update (rooted, unblocked and not bricked).
Yeah, upgrader or updater. One of those
1.ATRIX-in-PT said:
Hi live4nyy !
. The file is /system/app/Upgrader.apk ?
Click to expand...
Click to collapse
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
If you're in Titanium Backup, then it's called Updater 2.3.4.
If you've already downloaded the update, then you might also need to boot into recovery and wipe the cache partition to erase the update file.
live4nyy said:
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
Click to expand...
Click to collapse
this didnt work for me
das8nt said:
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
Click to expand...
Click to collapse
this did the trick
Yesss! No more annoying notifys!
hi all,
since the update was popping up from time to time and never really researched how to turn it off today, I friggin accidentally pressed on "install update" and automatically tried to reboot the phone, when I realized the mistake, I quickly pulled the battery out and waited for a few minutes then switched it back on.
it booted up fine but once it completes its bootup sequence, it would again prompt for an auto restart and try to install the update. Seems like the update is on the auto startup items (if there's such a thing).
I tried booting into safemode but can't get to do it maybe because I'm using an Alien build rom.
Any ideas on how to solve the problem? Please note that the phone boots but it tries to restart as soon as I can use it.
I have booted up now to recovery and will try to delete the updater apk and see if that will work. thanks in advance!.
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.
???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.
Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse
This is my only phone so I'm hoping someone can assist fairly quick. I have a One Plus Pro 8 that was stock ROM but rooted with magisk. I used Oxygen updater and had a notification to update to Aprils security update from what I'm guessing. I did the normal upgrade and then didn't reboot and then ran and installed magisk with the OTA method rebooted and all was working. Well stupid me forgot I had already done that and ran that again and now I'm stuck in a boot loop. Would anyone have access to the stock or modified boot.img for this device? I really hate to reflash all this as it takes forever to get my settings back to the way I like and haven't done this in nearly 2 years. At least re-setup my phone anyway.
GrandMstrBud said:
This is my only phone so I'm hoping someone can assist fairly quick. I have a One Plus Pro 8 that was stock ROM but rooted with magisk. I used Oxygen updater and had a notification to update to Aprils security update from what I'm guessing. I did the normal upgrade and then didn't reboot and then ran and installed magisk with the OTA method rebooted and all was working. Well stupid me forgot I had already done that and ran that again and now I'm stuck in a boot loop. Would anyone have access to the stock or modified boot.img for this device? I really hate to reflash all this as it takes forever to get my settings back to the way I like and haven't done this in nearly 2 years. At least re-setup my phone anyway.
Click to expand...
Click to collapse
So there are threads around here with patched and stock boot .img files.
You can also download most firmwares from here and unpack the .img files with a payload dumber.
Anyway, if you are on Android12 be very careful what you do in fastboot.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Firmwares: https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/
I didn't realize it was beta, yeah I tried to get one of those and extracted the boot.img and no go. It's obviously not toast using the MSM tool to restore. Now to look for a better ROM, I've been on the factory one since I got it.
GrandMstrBud said:
I didn't realize it was beta, yeah I tried to get one of those and extracted the boot.img and no go. It's obviously not toast using the MSM tool to restore. Now to look for a better ROM, I've been on the factory one since I got it.
Click to expand...
Click to collapse
Literally had the same problem as you. https://forum.xda-developers.com/t/something-went-horribly-wrong.4431335/
It sucked I've been in this for nearly 2 years but I backup my files to Google drive so that was the plus.