Related
I need to get recovery on my phone so that I can flash a rom because my USB isn't working cause it only charges. But is there any way I can do that? My phone is unlocked I just downgraded to android 2.3.3 so it's not rooted cause I need recovery so I can install superuser. Please help.
Use flash image GUI apk
frankie51 said:
Use flash image GUI apk
Click to expand...
Click to collapse
It says I need Root Access. I need to install superuser but I can't cause my USB isn't working.
go to your market and just download super user and after that download fom manager for free and once you open the first thing you see will be the flash recovery option which comes with the latest recovery. but you do need to be rooted in order to have custom recovery
-Da Reaper
I don't know of a way to root or flash a custom recovery without USB. Have you tried using a different USB cable? Maybe the cable you're using has gone bad as far as transmitting data.
Another way I just thought of is if someone can package up an update to the stock 2.3.3 ROM with root/superuser as update.zip that you can just download, place it the root of the sdcard, and use the stock recovery to update.
[email protected] said:
I don't know of a way to root or flash a custom recovery without USB. Have you tried using a different USB cable? Maybe the cable you're using has gone bad as far as transmitting data.
Another way I just thought of is if someone can package up an update to the stock 2.3.3 ROM with root/superuser as update.zip that you can just download, place it the root of the sdcard, and use the stock recovery to update.
Click to expand...
Click to collapse
The second option you listed sounds like as good as an idea as i'm going to get. If someone can package a stock ics rom for me with root/superuser i'll be greatly appreciated
if you have oem unlocked , then it is all possible , otherwise ... it can't be done
I have my OEM unlocked
qtwrk said:
if you have oem unlocked , then it is all possible , otherwise ... it can't be done
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
jpearn said:
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
Click to expand...
Click to collapse
go finding a original recovery dump,and flashing it in fastbootmode.
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
1
californiarailroader said:
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
Click to expand...
Click to collapse
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
lsnc said:
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
Click to expand...
Click to collapse
Thanks! However, the US Version doesn't have an update for it, at least not yet, and I haven't been able to find a stock US A700 ROM.
So we would need to rename the install-recovery.old back to install-recovery.sh in /system as this was disabled in CWM ??
So has anyone managed to successfully put on the stock recovery ?? !!
jpearn said:
So has anyone managed to successfully put on the stock recovery ?? !!
Click to expand...
Click to collapse
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Moscow Desire said:
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Click to expand...
Click to collapse
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
californiarailroader said:
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
Click to expand...
Click to collapse
Sounds like a plan I'll keep things working for now, thanks !
jpearn said:
Sounds like a plan I'll keep things working for now, thanks !
Click to expand...
Click to collapse
View attachment updater-script.rar
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
I don't understand these instructions. What original file is being replaced? What update.zip are you referring to?
EDIT
Well, I tried to swap out the update script that came in the ROM: SDs_Acer_A700_AV043.RV00RC00_AV043.RV07RC04_EMEA_CUS1, with the one provided above and seemed to have made some progress...I put on an external SD card and renamed to update and then flashed it through the CWM recovery and it completed. A random offset was noted and then the SD update completed note. However, when I rebooted the device it stuck at the Acer logo and never went any further.
EDIT
So, it then occurred to me that the flash through CWM was probably only partially successful - maybe the replacement of the recovery worked. So, I took the same ROM I noted above, unmodified, placed on the external SD card, renamed, etc. and flashed it and it worked - I never saw any signs of CWM during this process. I hope this helps others too.
EDIT
Looks like I spoke too soon...the flash never got past a 1/4 of the progress bar. Looks like I still have a non-functioning device.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
Hi, I'm a A510 user. I used the CWM to wipe data/factory reset, after that i cant flash any zip, and even cant enter the system. When i turn on the tab, it stuck on 'iconia tab' LOGO, I tried to hard reset, then i got a 'Unrecoverable bootloader error (0x19000008)'
I enter the fastboot and flash the stock recovery back. next i use the recovery to flash update.zip as usual, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway!
every time the flash stuck in the same place of the whole progress bar, i guess it is not an accident! After read your solution, I check the script in my zip, then i delete 2 lines about 'format' command. I think this time will be ok! but to my surprise the green turtle fell down when flashing.
I think the idea is great, but it maybe make the script incomplete, so it cant be flash in.:crying:
First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.
kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo
touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.
kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse
touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?
EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.
Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.
touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)
I was stupid. Point blank.
How can I get a ROM zip back on so I can flash it again?
It just hangs at the boot screen when I try to start up, but I'm able to get into TWRP recovery. Please help..I'm kinda freakin out.
Nothing showing on the internal card to be able to flash.
Trying to figure out how to maybe sideload? In ADB, the device doesn't show up...
I need baby step - by step
Vinsane said:
Trying to figure out how to maybe sideload? In ADB, the device doesn't show up...
I need baby step - by step
Click to expand...
Click to collapse
have you tried flashing the stock rom with fastboot?
crazynitro said:
have you tried flashing the stock rom with fastboot?
Click to expand...
Click to collapse
No I havent - how would i go about that?
It needs something to read to be able to flash...right now there's nothing on internal and wont mount to ADB
If I could flash via fastboot, would I be able to flash back the custom rom instead of the stock rom?
Vinsane said:
No I havent - how would i go about that?
It needs something to read to be able to flash...right now there's nothing on internal and wont mount to ADB
If I could flash via fastboot, would I be able to flash back the custom rom instead of the stock rom?
Click to expand...
Click to collapse
you dont need any anything to be able to flash. you just need a laptop with the asus drivers installed and the latest fastboot. I'm pretty sure you cant flash a custom rom with fastboot. i havent tried it myself but i wont take the risk. you could just flash the stock rom and then later intall the custom recovery and then go ahead and install the custom rom.
I think I got it. Thank GOD for the NEW TWRP recovery.
This is what I did. I poked around TWRP and noticed that I was able to change the storage location on where it looks to install. I thought...if I can load the zip to a micro SD and flash it from there..gravy.
Of course the day as it is...the SD reader on my comp stopped working..been running around the office trying to find on that did. Finally did...placed rom zip on it..rebooted into recovery..flashing right now as we speak
Praying and crossing fingers!
It freakin WORKED! I'm baaaaaack.
The only bad part is I lost my stock backup...but that's a small price to pay to have it working again.
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.