im new to this phone and unlocked and rooted, cwm, problem is it wont flash to partitions inside recovery, nor will it flash is fastboot, says cannot load????
any thoughts would be very helpfull
I don't understand. What are you trying to do? Flash CWM, it fails? Or do you already have CWM and you can't flash a ROM...?
Please explain in detail what you are trying to do, what you have attempted to fix it, and what error messages / info you get back.
Already have cwm after motochopper root method after bootloader unlocked, downloaded slim bean for sprint photon q, booted into recovery wiped partitions and flashed thing is it sticks at the bootanimation, so I waited for a bit after a fresh flash to no avail so I downloaded rds lite and necessary files to flash deleted the 2 lines in yhe xml file, went to flash comes up unknown flashboot command, tried a few times before I tried to flashboot flash twrp, but when I type the command to fasboot flash, error cannot load.img. either recovery or boot
Sent from my SM-T217S using Tapatalk
What version of RSD Lite are you using? 6.0+ is required AFAIK.
6.1.5 I do believe, afaik.... more info???
Sent from my SM-T217S using Tapatalk
turkbot said:
6.1.5 I do believe, afaik.... more info???
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
As far as I know.
Well that's odd - did you check the md5sum of the download? Make sure that you have a good download?
Can you give more details about your issue? Maybe a screenshot?
Yeah I can do that a little later
Sent from my SM-T217S using Tapatalk
Well i finally got my phone goin again, had to actually clean install my computer and adb, flashed twrp recovery and now running stock roooted for right now
PS i hate windows
Sent from my XT897 using xda app-developers app
Related
I just bought this phone yesterday and it is the i9020t (AWS version). The phone function works fine but every so often every application fails and gives an error asking to report it. I cannot manage to change the screen lock, it just comes back after reset. I only managed to remove it once. Also I cannot reset it no matter what I do, whether it is from settings or from the recovery menu. All data seems impossible to remove. How is this happening?
So Far:
-I got the boot loader unlocked (does this mean it is rooted yet?), failed to install superboot.zip
-Got the adb setup with using only part of the sdk files
(http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/)
Now I have tried this:
http://forum.xda-developers.com/showthread.php?t=884093
I can't get clockworkmod on here, I don't even know what it is exactly.
I believe I need to flash the phone onto stock firmware, the current seems corrupt as I can't do any changes such as password or wipe data.
More info on phone:
Android version: 2.3.4; Baseband version: I9020XXKD1; Kernel version: 2.6.35.7-ge382d80 [email protected]#1; Build number: GRJ22;
BTW I am on Mac OS X but can access a PC if I really have to.
Anything else I need to provide?
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
He said weeny hah but other than that he's right
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weeny very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
sinik420 said:
He said weeny hah but other than that he's right
sent from my nexus s on a kang from simms
Click to expand...
Click to collapse
Owned by auto correct
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It was a messed up phone. Returned it. Nothing would write onto sdcard. Which explains why it would not allow many functions that require data retention.
I flashed latest clockwork mod after installing brainmasters ics tweaked. When i noticed my mms wasnt working i decided to re flash another rom but when i booted into recovery it got back into fastboot mode and tells me "no boot or recovery img"
I have re flashed all versions through rom manager but they wont stick. I tried to push it with fastboot and my computer but my Ubuntu 11.10 wont recognize my Ns4g. I installed all the android sdk, adb, and fastboot files but when I type ./adb devices its doesn't come up with my device. ./fastboot flash boot recovery3101.img doesnt work either. Juat says <waiting on device>
flash image by GUI
search market for this app and use it to flash kernel image.
I'm on mobile
Sent from my Nexus S 4G using xda premium
1st. post in the correct section. This way you can get your answer quicker and you're not annoying everyone.
2nd. Find yourself a WINDOWS PC and install android SDK and all drivers for your phone to be recognizable. Then follow one of the posts in here to flash recovery.
You could also install ROM manager from the market and use it to flash recovery through it but its always good to have a proper SDK setup for this type of emergency.
This has happened to me before and I have fixed it by flashing the latest cwmr multiple times.
Try using a different USB cable if your com still doesn't recongize it.
PS now I use twrp and i like it a lot better
Sent from my Nexus S 4G using xda premium
I didnt see any other NS4g section. Sorry bud.
Would flash image gui work well to flash twrp?
When i use rom manager it says successfully flashes rom but then i reboot and get the sane no boot or recovery img. I dont have access to a windows pc...
Can a mod please move this to the nexus help section?
As stated, reboot from and get rom Manager from market. Try reinstalling recovery or scroll down and there is an option to use older versions and flash an older version.
Sent from my Nexus S 4G using xda premium
toddlmr said:
As stated, reboot from and get rom Manager from market. Try reinstalling recovery or scroll down and there is an option to use older versions and flash an older version.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Okay todd,
As stated before, back in my FIRST post i have rom manager and I havr flashed all versions of cwm available. 3.0.0.0 to 5.0.2.0 but none of them stick.
I just got flash image gui and tried to flash twrp and it said it was successful but when i rebooted i got the same no boot or recovery img
Make sure you have debug turned on.
Sent from my Nexus S 4G using xda premium
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
bnitty said:
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
+1 agreed it works like a lucky charm.
Sent from my BB GPA19x Linux S 4G using xda premium
might not be what you want to hear, but... maybe start from scratch again. find a guide that lets you revert to the stock image and then reroot. sometimes... you just have to start with a clean slate. good luck man. sounds like a stressful / annoying issue to have.
ehac1680 said:
Make sure you have debug turned on.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I never turn it off
bnitty said:
I had this happen to me when I first flashed a ICS port. the only thing that worked for me was to dl the Flash Image GUI from the market & flash your cwm file.
courtesy of my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
info[]box1 said:
+1 agreed it works like a lucky charm.
Sent from my BB GPA19x Linux S 4G using xda premium
Click to expand...
Click to collapse
I just tried to flash twrp and then cwmr 5.0.2.0 with Flash Image GUI and neither of them stuck...
Is it my only option to ask my friends if I can use their computer? I hate loading things on peoples computer. I feel bad...
mercado79 said:
might not be what you want to hear, but... maybe start from scratch again. find a guide that lets you revert to the stock image and then reroot. sometimes... you just have to start with a clean slate. good luck man. sounds like a stressful / annoying issue to have.
Click to expand...
Click to collapse
Im okay with starting over but I cant even get my computer to recognize my NS4G. I'm using Ubuntu 11.10 and I have Android sdk and fastboot on my computer but when I boot my phone into fastboot it isn't recognized by my computer. All "./adb devices" or "./fastboot devices" brings up is nothing!
If I can get my Linux machine to recognize my phone I would gladly return to stock unrooted and start over.
Flash twice in rom manager. See if that changes anything. Don't reboot between just one after another. Also, in rom manager hit menu and clear download cache before you try flashing.
info[]box1 said:
flash image by GUI
search market for this app and use it to flash kernel image.
I'm on mobile
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Its flash image GUI by joeykrim......
Sent from my Nexus S 4G using xda premium
Ochochinko said:
Im okay with starting over but I cant even get my computer to recognize my NS4G. I'm using Ubuntu 11.10 and I have Android sdk and fastboot on my computer but when I boot my phone into fastboot it isn't recognized by my computer. All "./adb devices" or "./fastboot devices" brings up is nothing!
If I can get my Linux machine to recognize my phone I would gladly return to stock unrooted and start over.
Click to expand...
Click to collapse
No ./ its just fastboot
So it should look like
# fastboot devices
# fastboot flash recovery recovery.img
Etc.
Sent from my Nexus S 4G using xda premium
This happened to me and I was freaking out until I updated super users binary then flashed clockworkmod and it worked fine.
Sent from my Nexus S 4G using xda premium
Oops didn't read both pages
I've had this happen to me several times. The problem happens any time I use an app (i.e. Rom Manager or Flash Image GUI) to flash a new recovery.
The only way I've been able to resolve it is to
1. Flash cwm 3.1.0.1 with fastboot
2. Go into recovery and flash cwm 5.0.2.0.
3. DO NOT update CWM when relaunching Rom Manager or like app.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
No ./ its just fastboot
So it should look like
# fastboot devices
# fastboot flash recovery recovery.img
Etc.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Either work if he is in the right directory.
@OP: Did you follow the Ubuntu guide to have it recognize your device? I'm on Ubuntu and everything works fine for me.
http://forum.xda-developers.com/showthread.php?t=883032
Greetz
Update: This bootloader is older and is not the newest available one. If you want the 4.18 version one go to THIS post and flash it with fastboot.
Older bootloader version: Doesn't flash and take hold for everyone, flash at your own risk
Usefull for people that don't want to flash in fastboot. The official OTA for 4.2 flashes this bootloader through recovery in the exact same manner
Code:
md5sum: 7cb16bc418e15ee2c7c48b82ea923e23
Code:
sha1sum: 6151d4afd075d03cfdfa33d111a1a6bba25fcab8
Code:
sha256sum: 2b7efeade37c1ec00d03ba71a56d5b921e6c27d4393298020bcd1601ae079605
Code:
sha512sum: cd7444ec7073e553b7715e4ee30d69f64b06ab3846f1d0ff3d9129f652ab4e90c3400f139a0347f0b78a0719c86b6e2d7f41d36068f032472dbc90c3530cefcb
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
remmyhi said:
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
Click to expand...
Click to collapse
I need to be aware of problems that happens on your Nexus7? I don't have that issue I flashed TWRP Recovery just fine on this booloader...
No, I did not write to you personally. Glad it worked on your side.
Just the people to know.
That's really strange. I would try flashing the 4.1.2 factory images even though it might wipe everything including your sdcard.
Sent from my Nexus 7 using Tapatalk 2
Did that, thanks. Indeed wiped everything
Glad I had a backup
Hey guys,
So, I can flash this file from TWRP and it will upgrade my bootloader?
Thanks in advance!
you can, but make sure you check MD5, flashing a corrupt download can kill your device. OP, you should add a MD5 check in the zip if possible. but thanks for this none the less.
If you have a rom like cm10 installed or other rom that has buysbox in it, just type busybox md5sum /sdcard/bootloader-grouper-4.13.zip
Either in terminal emulator or adb shell.
If your on stock you'll probably want to check it with a program on your pc or install busybox from one of the playstore busybox apps. Of course you'll need to be rooted.
Sent from my Nexus 7 using Tapatalk 2
I went ahead and added sha1sum, sha256sum and sha512sum checks.
I have just flashed the file and thank you, I no longer have to keep my power button pressed for 20 seconds just to have my tablet go on
Thank you so much!!!
If anyone has any problems there is a link in my SIG to fix it or if you just need to revert back...
Just a FYI the older bootloaders are in the factory images! You can extract them out and flash the bootloader separately if you don't want to flash ALL the factory images. So far flashing this with twrp I have not had one single issue yet to speak of... Each bootloader is meant to run on specific platforms, recoveries, kernels ect. So on that note I still suggest if you want to revert your bootloader you revert completely with the factory images.
Sent from my Nexus 7 using Tapatalk 2
Hi,
thanks for that but when i falsh it in TWRP it's wipe all my data but i still have the 3.41 bootloader?
I'm not sure if i understood the thing to do with the md5sum?
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
CWM + CM10 stable
I just flashed this bootloader using CWM 6.0.1.0 and CM10 stable. I used Chrome to download it and the md5sum command in terminal emulator to check the md5 hash before hand. It flashed fine, I have the new version number, everything continues to work. Very easy.
farshad.shirzadii said:
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=32735541&postcount=5039
Thanks, easy flash, works perfectly
Sent from my Nexus 7 using xda app-developers app
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
blucmal said:
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
When you power your device on you hold the volume down button to get into bootloader. On the main screen it will say what version it is.
Sent from my Nexus 7 using Tapatalk 2
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Xx
BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!
BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.
I currently can't use my usb port to receive data, so adb isn't an option.
I'm looking to flash the new PAC rom, and need to update my TWRP recovery from 2.6.0.0 to 2.7.0.8. I'm using HBOOT 2.19 if that makes a difference?
I want to use Flashify to do this as its my only option without using adb that I can see.
Has anyone here had experience using this? If it doesn't work I don't have any other way of restoring my recovery and my phone will dead weight.
Also will updating my recovery wipe the sdcard? I hope not as I need the rom file to survive to be able to bring my phone back to life, as sideload won't work for me.
Thank you for any help received on this.
Sent from my GT-I9000 using xda app-developers app
i could be wrong mate but I'm sure I've read you can get ADB to work over WiFi, think you have to enable it in developer options.. surely there is a tutorial kicking around someplace on XDA.
flashing new recovery.img shouldnt wipe. only Unlocking the bootloader, super wipe, flashing a ruu, factory reset - they all wipe the phone
ill have a look about and get back to you
**UPDATE**
Found this amongst many other tutorials, not sure if it will work but worth a try
http://forum.xda-developers.com/showthread.php?t=2570432 apparantly he has updated it to http://forum.xda-developers.com/showthread.php?t=2707556
there is also a twrp manager app (by jmz) on playstore, i think you can flash a new recovery direct fom the app ????
I had problems flashing a boot.img via flashify. Flashed successfully but got problems later. flashed via fastboot and everything was fine.
Many thanks for the input. Will try this when I get my phone back from HTC.
@Braddison
Can you flash recoveries thru the android os over adb? Thought you had to do that thru hboot.
@theodorius123
What exactly did you try to flash with Flashify?
Sent from my GT-I9000 using Xparent Red Tapatalk 2
no idea what it was exactly, only know that it was a boot.img - as i wrote before
Not sure, but check out jmz app on play store.... Twrp manager I think you can do it from that or try goo manager, also on play store. i'm sure you can flash new recoveries directly from within these apps?
Good luck
twrp = https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
goomanager = https://play.google.com/store/apps/details?id=com.s0up.goomanager
again not sure as i haven't tried them myself
Or this one: http://forum.xda-developers.com/showthread.php?t=2730305
Ah! Forgot about the aroma recovery installer. That's a great option. Then it should just be a matter of flashing rom. Are you s-off? If so shouldn't need to flash boot. Img afterward
I am s-off. Think the aroma installer is my best bet. But I may not bother just because its to much of a risk without being able to use fastboot to restore things in case something goes wrong...
Bloody HTC.
Sent from my GT-I9000 using Xparent Red Tapatalk 2