I have spent a couple days searching for an answer to my question and although I found some, they were not exactly what I was looking for so sorry for a new thread.
I bought the i9020A for my niece and it was running 2.3.4. I tried to force the 4.0.4 OTA update but after some reading I came to the conclusion that I needed to be on a different version and it would not work on 2.3.4. After messing around I gave up and did this.
http://forum.xda-developers.com/showthread.php?t=1653713
She is having issues with dropping signal, and very slow messaging. She also reported that a couple of times she received an error that said "relaunch Me". I have never heard of that issue. What I want to do is just use the factory image to put her on 4.0.4 and in line to get the OTA in the future. She doesn't need a custom recovery anyway. I want her on stock. I have the SDK and everything, bootloader unlocked, fastboot installed. I download the image from Google Which I believe should be "Factory Images "sojua" for Nexus S (850MHz version, i9020a)" because her model is the i9020A and using it on ATT. At this point is where Im a little lost. I think it should be easy at this point but i cant find a good how-to on exactly what to do. I used this one
http://forum.xda-developers.com/showthread.php?t=1572307
but the english is kind of broken and frankly dont understand it enough as a somewhat noob. Really 2 is what I dont understand. I extract the files and move them in the entirety to android-sdk/platform-tools/. I get that. But then he says "run a cmd and moves in "platform-tools" folder"...what?? Is he saying change directory? Thats what I assumed but again, didnt want to break something.
Finally, do I need to flash KB3 radio or is the radio with 4.0.4 on this device fixed for proper hspa+ like speeds? Basically from a 200k to a 1.5meg average. I have read people complaining about the radio and dropped signal as well, but havent found any that talk about it after running on stock 4.0.4. Shes a teenager and doesnt need bleeding edge, but if the speeds are that different than Ill happily give her a better radio if possible.
Anything other suggestions would be great so that I can give her a tip top device. Thanks again!
https://developers.google.com/android/nexus/images
the instruction are on the same page ..
all you need is fastboot (make sure it is in your path, meaning : if you type -just- fastboot in a command -or terminal - you don;t get "command not found" -or somthing simimilar-. there is a script in the zip tat will do all (flashall.sh, on mac and linux it works just fine, On windows I don;t know, worst case open if in notepad and see what it does -- if I remmeber it is 3 -4 lines long- and tyupe the commands yourself )
do know that this will erase anything and everything on the device.
--
PS: flashall.sh does this :
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Click to expand...
Click to collapse
if fastboot is not in your path, just copy it in the folder where you extracted the factory image file (should be "sojua-imm76d") and replace "fastboot" above with "./fastboot" if you're on a mac/linux or "fastboot.exe" if your on windows.
Do what he said
Hit the thanks button
I'm on Windows so I'll try what your saying. My fast bot is in the tools folder, should it not be? So basically I have to be at that directory for it to work but have used it.
Sent from my Galaxy Nexus using Tapatalk 2
kenshin33 said:
https://developers.google.com/android/nexus/images
the instruction are on the same page ..
all you need is fastboot (make sure it is in your path, meaning : if you type -just- fastboot in a command -or terminal - you don;t get "command not found" -or somthing simimilar-. there is a script in the zip tat will do all (flashall.sh, on mac and linux it works just fine, On windows I don;t know, worst case open if in notepad and see what it does -- if I remmeber it is 3 -4 lines long- and tyupe the commands yourself )
do know that this will erase anything and everything on the device.
--
PS: flashall.sh does this :
if fastboot is not in your path, just copy it in the folder where you extracted the factory image file (should be "sojua-imm76d") and replace "fastboot" above with "./fastboot" if you're on a mac/linux or "fastboot.exe" if your on windows.
Click to expand...
Click to collapse
So wait, im supposed to replace "fastboot" with fastboot.exe so fastboot flash bootloader bootloader-crespo-i9020xxkl1.img would look like fastboot.exe flash bootloader bootloader-crespo-i9020xxkl1.img? That doesnt seem right.
TheIowaKid said:
So wait, im supposed to replace "fastboot" with fastboot.exe so fastboot flash bootloader bootloader-crespo-i9020xxkl1.img would look like fastboot.exe flash bootloader bootloader-crespo-i9020xxkl1.img? That doesnt seem right.
Click to expand...
Click to collapse
yes, assuming that the file "fasboot.exe" is in the same directory as all those other files (img files) just open a cmd window change to where you extracted the files ( cd path_where_you_extracted_the files, or in some wversion of windows in the explorer, witgh click and open cmd here --or something like that-, and type the commands one bye one (after rebooting the on bootloader mode -- turn it off and press vol up while still pressing vol up press power and hold it,-- )
So I actually put the .exe in the command line after the word fastboot? This may explain why it didn't work for me the first time! Also on a side not do I need to worry about cache or dalvik in this scenario or can I just take her phone, enable debugging, and do this knowing it will wipe everything?
Sent from my Galaxy Nexus using Tapatalk 2
TheIowaKid said:
So I actually put the .exe in the command line after the word fastboot? This may explain why it didn't work for me the first time! Also on a side not do I need to worry about cache or dalvik in this scenario or can I just take her phone, enable debugging, and do this knowing it will wipe everything?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yes, after "fastboot" --fastboot.exe--
this will wipe everything (it will put the phone in the same state you first got it it, except the bootloader, which will stay unlocked --
Happy to report back that everything worked as planned. I didn't have to add the .exe I simply made sure everything was in the same folder; adb, fastboot, and all the extracted files from the download. Took like a minute total. A follow up though, she still seems to have issues with the radio. I would need to put a custom recovery on in order to flash a radio, correct?
Sent from my Galaxy Nexus using Tapatalk 2
TheIowaKid said:
Happy to report back that everything worked as planned. I didn't have to add the .exe I simply made sure everything was in the same folder; adb, fastboot, and all the extracted files from the download. Took like a minute total. A follow up though, she still seems to have issues with the radio. I would need to put a custom recovery on in order to flash a radio, correct?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
not if you get the img file. one the steps you just performed was flashing a radio img
"fastboot flash radio radio-crespo-i9020uckj1.img" <-- this one to be precise.
there should be a thread in one of the forums that has of all the official Roms (with radios and everything, full and incremental), I think it is in the general section, there should be instructions on how to flash a radio image.
I can't find the thread in question but the link you provided in your first post has 2 of them, the one you just flashed and the previous one (UCKF1)
just download the the factory image you want do exactely what you did b4 except flash only the radio img (ie : fastboot flash radio some_radio_image.img)
you can find some here too : http://www.randomphantasmagoria.com/firmware/nexus-s/i9020a/
KB3 is the radio that I keep seeing pop up. Is that the good one?
Sent from my Galaxy Nexus using Tapatalk 2
frankly I wouldn;t know, I'm using the latest one (From the last OTA I think) I've never had any problems with it. try and see, you can always flash an other one.
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.
I tried using revolutionary to root the phone and its worked for my phone and about 4 others ive done. but this peticular phone i came across it will read it, give me a code but tell me that i inputted the.wrong code and close. i did this a few times same.result. so i went to htc.com and unlocked the bootloader and i when i try to install the custom recovery the rough the bootllader it tells me.the phone is not recognized after it picks up the file and opens it. what the #$%$# is going on? lol
Chances are you've made a typo somewhere with Revo, and with unlocking via HTC you have to manually flash CWM to be able to flash a ROM
i tried like ten times and it keeps telling me key is incorrect.
i feel doing it manuelly is the only way to go. since the bootloader is unlocked i downloaded the recovery and saved it to the root. i turned on the phone to the bootllader, it reads it, and it says device not recognized. is their a .img file i can use instead? and what are the adb commands so i can flash it that way?
There are threads covering adb on here, and just Googling it will give you what you want to know as well.
What version of Revolution are you using? Could be an older one which has a different beta key than the current v0.4
adb way is manually
make sure you have sdk and adb/fastboot set up in your environment, its lot faster that way
once you have that, put the phone in fastboot
and type
fastboot flash recovery (drag the recovery.img in command window) and press enter and it will flash new recovery
HHHHHHHHEEEEEECCCCCKKK YYYYEEEESSSS!!!!
Thanks bro!!!!
I put the reocevery into c:/android
Ran cmd
fastboot flash recovery recovery.img
perfect
thx again!!!
Welcome and happy Rom flashing
[email protected] said:
i tried like ten times and it keeps telling me key is incorrect.
i feel doing it manuelly is the only way to go. since the bootloader is unlocked i downloaded the recovery and saved it to the root. i turned on the phone to the bootllader, it reads it, and it says device not recognized. is their a .img file i can use instead? and what are the adb commands so i can flash it that way?
Click to expand...
Click to collapse
Copy/paste the key to notepad then copy/paste from notepad to revolutionary then it will work.
My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?
The bootloader was already unlocked when I got the phone.
Thanks for this. I will test it and add it to my guide.
VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?
gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.
Okay, got it.
Too many things floating through the intertubes with similar filenames.
gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.
S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!
I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .
signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.
You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked
to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.
A week ago I faced this error for the first time but didn't have the time to take a look at it so I just downloaded Air Droid as a temporary solution. But then more problem appeared. The battery indicator wasn't working so I decided to fix it somehow. To dig on Google. I tried flashing different ROMs and recoveries and on and on. the problem is that I'm now stuck on bootloader. I have no system installed and that crappy TWP won't start. The splash screen just flashes and that's all. So my phone is now a brick and I just don't have any more ideas. I need to lock my bootloader somehow so I can take it back to Samsung establish some kind of USB connection so I can install a new atleast,
Any help would be very much appreciated.
Zunex
anyone?
Zunex95 said:
anyone?
Click to expand...
Click to collapse
Hello,
I assume you are using a windows pc (correct me if i'm wrong)
Use this forum > http://forum.xda-developers.com/showthread.php?t=1901617 to install drivers for your nexus s.
Afterwards, reboot your PC
Do you have adb installed? If so skip this part:
Install minimal adb and fastboot using this forum > http://forum.xda-developers.com/showthread.php?p=42407269
Try inputting fastboot devices into the terminal window and see if your device shows up
Then you can flash everything back to stock. You can do this by following the following steps:
Go to this link and download the appropriate files for your nexus s >https://developers.google.com/android/nexus/images
Use a program such as 7-Zip to open and uncompress the package to a folder of your choosing
Navigate to that folder and try clicking flash-all.bat
Hopefully that will flash your whole phone back to stock. If not you will have to manually flash each part. Do this by typing the following into the terminal, one by one, replacing the file names with the appropriate ones for your nexus s.
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
For example, for the first line of code, I would go into the uncompressed folder and hold down shift while right clicking the bootloader file. I would then select “copy as path”. Then I would go back to the terminal and type “fastboot flash bootloader ” then paste the path I just copied. I would then repeat for the rest of the items.
Feel free to ask questions if it does not work. Ill try to reply as soon as possible. Cheers.
Thanks I solved it. The problem was with my phone's USB port. Atleast the usb module/part of the port. I put a little metal in it then moved it around a couple times.. tried to save it. Somehow I got it working again, so I instantly flash a working recovery then went back stock. I returned my device to Samsung (It was under warranty) and they fixed it.
Cheers
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?