[Q] Clean fastboot Flash for nexus s after soft bricking - Nexus S Q&A, Help & Troubleshooting

[Q]
Hi,
I have nexus s GRJ22 Android 2.3.4 I904. I tried rooting it using clockwork and super user but after doing that when i reboot It stays in the google logo. I could find that i was not able to mount system in the clockwork recovery with means that its not having sufficient permissions .
1. Factory reset - not working
2. Tried fixing permissions - not working
3. tried remounting - not working
what i'm possible to do is get into fastboot mode and clockwork recovery mode and in the normal booting it stays at the google logo.
with this i can say i messed up something when i was rooting. and the phone is useless now.
The last option i know now is fastboot flashing of all the images (boot, system, recovery). How to flash everything finally and bring it back to the state which I got from the factory?
I'm looking for if any one has theses images so that I can fastboot flash it and bring it back in an operating condition.
I'm new to android development, android devices and a noob.
Please do ask If you guys need any more info.
I appreciate any answers and thanks for reading my question.

First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.

suksit said:
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
Click to expand...
Click to collapse
Thanks for the reply.
its not I904 I'm sorry its I9020 which is the model number of the phone.
I tried the link that you had posted already but it stops at getprop function in the script when i do the update and says status 7 error and the update fails because the /system is not mounting.
Kindly suggest me to bring this phone back.

Hmm, I still have the impression that you have the incorrect version of CWM. What is your service provider? As far as I remember, the I9020T and I9020A require a different version of CWM. And also what is the version of CWM installed?
If you've got the I9020T, try installing this one (from kouch's site)
But if you've got the I9020A, you should try the recovery from this guide (Part 3 - Recovery)

Sorry for the delayed response ,
I have the Tmobile carrier and its I9020T. The version of CWR is 3.0.2.4 which is running. As i said before its not monting the /system.
any other options that I have. ?
Please suggest
Thanks for your time..

I got the nandroid for GRJ22 I9020T.
I'm unable to fastboot flash boot boot.img from this ROM.
it says FAILWrite..
also tried to do the same way for system.img it says Invalid Magic Code !

thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..

rakeshpatil1983 said:
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
Click to expand...
Click to collapse
Glad you made it!

Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..

rakeshpatil1983 said:
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
Click to expand...
Click to collapse
your phone was never bricked. bricked means itll never ever work again. if your planning on using it later and using it now, then bricked is definitely not the right word to use ;-)

well then its appropriate to say
"It was broken for two days"

nexus S was in locked state...can't able to unlock thorugh "fastboot oem unlock" (FAILED <remote:ERASE FAIL>.. even all drivers were installed properly...if i try to get in to recovery mode there is an exclamtion mark...what it that..??? plzzzz help me with this

Related

i cant do Recovery

hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.

I believe I bricked my phone.. NEED HELP !

So i guess I felt out of date and wanted to root my phone and use that cm10 rom or whatever everyone else is and i messed it up real bad. I keep getting this msg "this build is for development purposes only do not distribute outside of htc.." on the loading screen. At this point i just want to restore it back to normal , idc if i lose data , i just want my phone to WORK! I've flashed a clean recovery.img but whenever i try to access recovery , it brings me back to that screen with the red words. In addition , my phone is rogers so i can't even find a correct RUU to install. Does anyone have any suggestions as to how I can get my phone to work again ? Any help is greatly welcomed !
P.S Wow i think it got worse , now it doesnt even loop again , it goes start into that menu bootloader, reboot , power down.. Omg i spent 5 hours looking into this. I NEED HELP!
Lasts3cond said:
So i guess I felt out of date and wanted to root my phone and use that cm10 rom or whatever everyone else is and i messed it up real bad. I keep getting this msg "this build is for development purposes only do not distribute outside of htc.." on the loading screen. At this point i just want to restore it back to normal , idc if i lose data , i just want my phone to WORK! I've flashed a clean recovery.img but whenever i try to access recovery , it brings me back to that screen with the red words. In addition , my phone is rogers so i can't even find a correct RUU to install. Does anyone have any suggestions as to how I can get my phone to work again ? Any help is greatly welcomed !
P.S Wow i think it got worse , now it doesnt even loop again , it goes start into that menu bootloader, reboot , power down.. Omg i spent 5 hours looking into this. I NEED HELP!
Click to expand...
Click to collapse
..... It says that on every One X, it's HTC telling whoever turns the phone on that you used HTCDev.com
Make Sure you have TWRP (recovery) flashed/installed ... then in the bootloader go into recovery and flash cm10 ... and since you probably have the newer hboot 1.14 that means that you HAVE to flash the kernel (boot.img) via fastboot
Which is simple,
flash cm10
then reboot into the bootloader > fastboot
extract the boot.img from the cm10.zip
and fastboot flash boot boot.img
then your done reboot and enjoy.... (anything else read threw the forum, all your answers have been asked by somebody else already)
On rogers he won't have the 1.14 hboot, which means all he has to do is install the rom.
Try flashing the recovery again (TWRP ONLY!)
And then reinstall CM10
Tachi91 said:
..... It says that on every One X, it's HTC telling whoever turns the phone on that you used HTCDev.com
Make Sure you have TWRP (recovery) flashed/installed ... then in the bootloader go into recovery and flash cm10 ... and since you probably have the newer hboot 1.14 that means that you HAVE to flash the kernel (boot.img) via fastboot
Which is simple,
flash cm10
then reboot into the bootloader > fastboot
extract the boot.img from the cm10.zip
and fastboot flash boot boot.img
then your done reboot and enjoy.... (anything else read threw the forum, all your answers have been asked by somebody else already)
Click to expand...
Click to collapse
Can you post download to to what you're refering to ? I want to delete all my old files and redownload it all, starting fresh.
ugh crap im so lost , i don't get what to install like .. i flash CWM and it doesnt work and all that omg . Can we skype or somethng so we can do this step by step ? :$
Lasts3cond said:
i flash CWM and it doesnt work and all that omg
Click to expand...
Click to collapse
That might be your problem. CWM isn't supported for this phone and has been known to corrupt data.
Links for all the files you need are in a sticky in the Development forum. Here's the link for TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
Once you've got that, you can wipe your phone inside TWRP (don't do it in bootloader--you'll have to reformat your sd card), and reflash CM10.
That link requires me to use that GOO manager? Confused lol i have TWRP on my computer but not sure the steps to use it ..
Lasts3cond said:
That link requires me to use that GOO manager? Confused lol i have TWRP on my computer but not sure the steps to use it ..
Click to expand...
Click to collapse
You can't use Goomanager if the phone doesn't boot. You need to push it over to your phone using adb, then you can flash it from recovery.
redpoint73 said:
You can't use Goomanager if the phone doesn't boot. You need to push it over to your phone using adb, then you can flash it from recovery.
Click to expand...
Click to collapse
Lol yeah i understand that and adb? I can't even past the screen where it shows fastboot , factory rest , shut down .. etc
Lasts3cond said:
Lol yeah i understand that and adb? I can't even past the screen where it shows fastboot , factory rest , shut down .. etc
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1754018
iElvis said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Beat me to it.
Read up, get adb working. Then you can install TWRP using adb.
So first i need to get adb working , then install TWRP to wipe my phone? To access that i flash TWRP and go into recovery right ?
EDIT: So .. i've downloaded that adb , and i got a bunch of files.. what do i do with this? I put them into my fastboot folder in my C drive.. Also i need to unlock my phone to do this right ? Cause i accidently relocked it .
EDIT: OKAY i rooted my phone , and got into TWRP , tried a factory rest under the wipe menu. http://i48.tinypic.com/13yklep.jpg It says fails.. what do i do ?
Go to mount usb storage (not sure which screen its on) while it's plugged into your computer
If windows says the card is corrupted, format it fat32, then copy over a rom onto your sd card
area51avenger said:
Go to mount usb storage (not sure which screen its on) while it's plugged into your computer
If windows says the card is corrupted, format it fat32, then copy over a rom onto your sd card
Click to expand...
Click to collapse
Okay got into mount http://i47.tinypic.com/2cq085x.jpg then a screen pops up , is this the one? http://i45.tinypic.com/m7ur08.jpg
EDIT: Okay so i need to copy a rom onto my phone via usb. Do i copy over the boot.img,system and NETA-INF from cm10 ?
So i put the cm10 zip onto my sdcard (my phone) and i got this when i want to install .. should i proceed? http://i45.tinypic.com/28uts7n.jpg
WAIT NOOOOO
That is an international rom
Get CM10 from THIS FORUM ONLY
http://forum.xda-developers.com/showthread.php?t=1790032
area51avenger said:
WAIT NOOOOO
That is an international rom
Get CM10 from THIS FORUM ONLY
http://forum.xda-developers.com/showthread.php?t=1790032
Click to expand...
Click to collapse
LOL okay ! But on that thread isnt that cm10 for AT&T HTC XL? :S I have a Htc one x rogers .
Lasts3cond said:
LOL okay ! But on that thread isnt that cm10 for AT&T HTC XL? :S I have a Htc one x rogers .
Click to expand...
Click to collapse
The Rogers HTC One X IS a HTC One XL. Rogers just branded it. The OneX has the Tegra 3 Quad Core Processor, the One XL has the S4 Dual Core Processor. Your phone is the same as the ATT Version. Trust me
Okay got the evita one but it still says same msg , should i proceed? :S
lasts3cond said:
okay got the evita one but it still says same msg , should i proceed? :s
Click to expand...
Click to collapse
omfg it works ty so much!
No problem. Just be glad you didn't flash an international Rom. They can render your device completely unusable. Remember only flash things from this forum and enjoy
Sent from my HTC One XL using xda app-developers app
area51avenger said:
No problem. Just be glad you didn't flash an international Rom.
Click to expand...
Click to collapse
After all that, lol. At least he had the sense to stop and ask.

Cant access recovery. Have nandroid but cant flash it.

Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
ksflat43 said:
Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
tactical kitten said:
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
Click to expand...
Click to collapse
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
ksflat43 said:
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
Click to expand...
Click to collapse
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
tactical kitten said:
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
Click to expand...
Click to collapse
I cant install through fastboot. I get the "error cant load" message i talked about in the first post. It wont let me near recovery
if u can get in to fastboot but not in to twrp youll probly have to relock your bootloader and ruu back to stock
Reflash twrp 2.3.3.1 for evita in fastboot, also run fastboot erase cache. If your nandroid was made with cwm it wont work with twrp.

[solved] [Q] stuck at bootloader warning

i got stuck at unlocked bootloader warning message.
i got FC's of android system after installing fabiotera's battery percentage Mod..it was for brazil versions.. i did it to my Indian version..now its not even entering in.just got stuck at warning message... my phone was unlocked,rooted,with Cwm installed.. i dont have a nandroid backup.. i had a messed framework..so i tried to flash firmwares..it was little bit difficult.. someone help me with this..
i want to flash asian firmware or i should move some rom inside it.. i cant even copy rom to the phone.as it didnt even show as a portable drive
edit : i resolved this thing..thanks neozen and
This command helped me
'' fastboot -S 256M flash system system.img ''
..
Happy happy..
techmachi said:
i got stuck at unlocked bootloader warning message.
i got FC's of android system after installing fabiotera's battery percentage Mod..it was for brazil versions.. i did it to my Indian version..now its not even entering in.just got stuck at warning message... my phone was unlocked,rooted,with Cwm installed.. i dont have a nandroid backup.. i had a messed framework..so i tried to flash firmwares..it was little bit difficult.. someone help me with this..
i want to flash asian firmware or i should move some rom inside it.. i cant even copy rom to the phone.as it didnt even show as a portable drive
Click to expand...
Click to collapse
If you can at least go to Download (bootloader) mode, I recommend you go back to Stock by following the instructions in this post:
http://forum.xda-developers.com/showthread.php?t=2542219
Otherside, if you don't want to start over and can go to CWM, you can sideload a ROM...
Good luck!
Thanks for your reply neozen
i searched for sideloading tutorials..
In that it has been mentioned that mount /sdcard
How do i do that..
in our cwm,twrp reoveries there is only mount system.fsg,firmware...etc bt not sdcard..
can you or someone mirror me the latest asian dual sim firmware to google drive..??
Becoz that site gives me slow speed..
techmachi said:
Thanks for your reply neozen
i searched for sideloading tutorials..
In that it has been mentioned that mount /sdcard
How do i do that..
in our cwm,twrp reoveries there is only mount system.fsg,firmware...etc bt not sdcard..
can you or someone mirror me the latest asian dual sim firmware to google drive..??
Becoz that site gives me slow speed..
Click to expand...
Click to collapse
No no no... you don't need to mount anything if sideloading!
All you need to sideload is a working adb connection while in CWM or TWRP.
Sideloading is using your computer to send the .zip file you want to flash without having the file on your phone!
I don't use it much myself, because in CWM/TWRP, you could just use ADB to push the file to your phone as well..
I don't know what ROM you trying to use for your phone, STOCK or custom?
But I think you can find the latest (Android 4.3) Dual-SIM ASIAN ROM here.. http://www.filefactory.com/folder/c6cdedc45a775d27
It's the last one on the 1st page in the list: fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar.gz
Follow the instructions carefully in the guide on how to restore back to stock!

[Resolved] Installed TWRP on phone with a locked bootloader - now stuck in boot loop

I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.

Categories

Resources