Related
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.
ih guys i bought a nuxus s for at&t on ebay, the phone is in good condition and the phone has jelly bean
on it so i was really happy to buy the phone what the seller didn't say is that the phone is rooted and jelly bean on the
phone is a rom and not a stock ota and now what im worried about is that jelly bean on this phone is kinda buggy and i
don't know if that's just the rom or if this how stock jellybean is? And with the rom i have will i get updates from Google in the
future or i'm i stuck with what i have, what should i do? any help is appreciated!
Kernel looks like the stock one. Have you tried a factory reset yet? If you're still unsure, you can get the stock images from here
https://developers.google.com/android/nexus/images
Decompress and take out the images you need and flash via fast boot. Its hard to type it all via phone, but a quick search will help you with everything you need.
chronophase1 said:
Kernel looks like the stock one. Have you tried a factory reset yet? If you're still unsure, you can get the stock images from here
https://developers.google.com/android/nexus/images
Decompress and take out the images you need and flash via fast boot. Its hard to type it all via phone, but a quick search will help you with everything you need.
Click to expand...
Click to collapse
OK i have tgz file do i deconpress it on the my phone or computer and do i do this through boot loader or rom manager, sorry rookie here.
I just hopped on my PC, so I'll do my best to help. Any veterans feel free to correct me, please . Make sure if you set anything up, back it up via recovery and then wipe the phone :
1. Need to do this via the PC(assuming you have ADB and android SDK)
2. Open the tgz file.
3. Remove the boot.img, bootloader.img, radio.img, system.img and recovery.img. He probably has the current bootloader, but I would flash it just to be sure.
4. Reboot into the bootloader(vol up+power button)
5. Open up cmd prompt and get to adb. Ensure your device is recognized by typing fastboot devices
6. Once you're squared away with that, type fastboot flash bootloader bootloader.img
7. Fastboot flash boot boot.img
8. Fastboot flash system system.img
9. Fastboot flash recovery recovery.img
10.Fastboot flash radio radio.img
I don't know if there is any particular order those need to be flashed, but once you're done, reboot the phone, set it up, and enjoy.
mattrc77 said:
OK i have tgz file do i deconpress it on the my phone or computer and do i do this through boot loader or rom manager, sorry rookie here.
Click to expand...
Click to collapse
Here is a thread that will help you flash that on your phone.
http://forum.xda-developers.com/showthread.php?t=1785672
You decompress it on the computer then flash it with fastboot to your phone.
Apparently I've given out too many thanks today. I forgot about that link and typed all that crap out. lol
thanks guys !
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
stedrocklp said:
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
Click to expand...
Click to collapse
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Thank you Thank you Thank you!
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
That was definitely the problem and I had been trying everything for the past two days. I appreciate you taking the time to reply.
asus tf300 help
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Did I brick it?
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
solution
mizifih said:
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
Click to expand...
Click to collapse
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
jijitax4 said:
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
Click to expand...
Click to collapse
What if you can only boot to APX mode? I only have the option of using that because my unlocked bootloader got erased in the process of updating to JB. Is there a way to install a bootloader using fastboot? Or will it only work with an existing bootloader?
In other words, when I issue the fastboot command
fastboot -i 0x0B05 flash system blob
I get "waiting on device" and nothing happens after that.
Thank you, this worked !!!!!!
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?
Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.
Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk
This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more
Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0
No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.
So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?
Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck
Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?
Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.
For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....