Related
I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.
Hey guys, Hopefully somebody can help me here.
Basically i flashed & rooted my D802 to 4.4.2 using this method > http://forum.xda-developers.com/showthread.php?t=2680789
All was running fine however somewhere along the line something has messed up! I tried to boot into recovery and now im hit with "Secure Booting Error! Cause : boot certification verify" instead of TWRP!
Ive tried to use this method > http://forum.xda-developers.com/showthread.php?t=2625044 to flash back to stock and unroot BUT when i get to step 5. of method 1. instead of asking to to Select Country & Language it starts the LGMobile Support Tool and the tool tells me i have the latest available software for my device.
The phone is running fine and i can get into download mode.
Thanks in advance for any help.
Anybody got any ideas?
OK ive managed to boot into recovery(TWRP v2.6.3.3)I was gonna try to push a new ROM to my device via ADB sideload, When i select the ADB sideload feature TWRP just gets stuck on "Starting ADB sideload feature..." and sideload wont start!
Anybody got any ideas?
Thanks.
ATOJAR said:
Hey guys, Hopefully somebody can help me here.
Basically i flashed & rooted my D802 to 4.4.2 using this method > http://forum.xda-developers.com/showthread.php?t=2680789
All was running fine however somewhere along the line something has messed up! I tried to boot into recovery and now im hit with "Secure Booting Error! Cause : boot certification verify" instead of TWRP!
Ive tried to use this method > http://forum.xda-developers.com/showthread.php?t=2625044 to flash back to stock and unroot BUT when i get to step 5. of method 1. instead of asking to to Select Country & Language it starts the LGMobile Support Tool and the tool tells me i have the latest available software for my device.
The phone is running fine and i can get into download mode.
Thanks in advance for any help.
Click to expand...
Click to collapse
The ROM you flashed is from my thread. I'm not sure why you think custom recovery remains available? Unless I've missed something else you did. It is overwritten by the stock ROM when flashed. Hence I clearly stated that custom recovery will no longer be available.
I don't know what "messed up" with the ROM?
I suggest you revisit the page you used and try the alternative method if you really fell the need to downgrade...
Well after 5 house of messing around i managed to ADB push CM11 too my device, Boot the phone then connect to my PC then re-flash 4.4.2 & root using this method > http://forum.xda-developers.com/showthread.php?t=2680789
Think ill just stick to 4.4.2 lol.
ATOJAR said:
Well after 5 house of messing around i managed to ADB push CM11 too my device, Boot the phone then connect to my PC then re-flash 4.4.2 & root using this method > http://forum.xda-developers.com/showthread.php?t=2680789
Think ill just stick to 4.4.2 lol.
Click to expand...
Click to collapse
Yes, that's my ROM...
Sent from my LG-D802 using XDA Premium 4 mobile app
So i got my brand new verizon Lg G2 Yesterday, straight from verizon. It came stock Running VS98012B, Build number JDQ39B, Android 4.2.2.
I ran it completely stock for a little bit, and loved it. But ima crack flasher, and cant run stock for long. So i decided to root. I Used ioroot24 With a few hiccups(ADB drivers wouldnt install with windows 7, So i had to boot into windows xp and do the process).
So im now running the same software with a completely functioning and full root. Next step was to install TWRP or Cwm(philz). I followed WACOmalts Guide.... with no success.
(http://forum.xda-developers.com/showthread.php?t=2449670) This one.
Option 1 Goes good until this step
"./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img"
It always says something failed (Not sure about the message Because i cant repeat it now) Or it gives me a list of commands, as if i typed "adb"
Option 2 I can follow completely through with no errors, But rebooting into recovery always brings me to a black screen.
Ive tried the 2.6.3.1 and the 2.6.3.2 .img files with so success. So i downloaded both 2.6.3.3 and 2.7.0.0 zips and extracted the recovery img and tried using those files. Still a black screen.
Option 3 Just dont work for me.
Has anyone Had his trouble before? Im not a huge noob, Ive had a optimus l9, galaxy nexus, and htc incredible 4g, All with working recoverys So im sure i have enough knowledge. Please Help!
s-chassis said:
So i got my brand new verizon Lg G2 Yesterday, straight from verizon. It came stock Running VS98012B, Build number JDQ39B, Android 4.2.2.
I ran it completely stock for a little bit, and loved it. But ima crack flasher, and cant run stock for long. So i decided to root. I Used ioroot24 With a few hiccups(ADB drivers wouldnt install with windows 7, So i had to boot into windows xp and do the process).
So im now running the same software with a completely functioning and full root. Next step was to install TWRP or Cwm(philz). I followed WACOmalts Guide.... with no success.
(http://forum.xda-developers.com/showthread.php?t=2449670) This one.
Option 1 Goes good until this step
"./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img"
It always says something failed (Not sure about the message Because i cant repeat it now) Or it gives me a list of commands, as if i typed "adb"
Option 2 I can follow completely through with no errors, But rebooting into recovery always brings me to a black screen.
Ive tried the 2.6.3.1 and the 2.6.3.2 .img files with so success. So i downloaded both 2.6.3.3 and 2.7.0.0 zips and extracted the recovery img and tried using those files. Still a black screen.
Option 3 Just dont work for me.
Has anyone Had his trouble before? Im not a huge noob, Ive had a optimus l9, galaxy nexus, and htc incredible 4g, All with working recoverys So im sure i have enough knowledge. Please Help!
Click to expand...
Click to collapse
Just ran into the same issue it doesn't seem like anyone has an answer for this yet, some from this thread http://forum.xda-developers.com/showthread.php?t=2584052
said they were able to just flash back to stock and do everything over and it worked but I was looking into to that but the KDZ method is apparently broken at the time and for the TOT method to restore I can't find a VS98012B (latest VZ firmware so far) TOT file to use for the restore so I don't break anything else.
I'll see what I can find and let me know if you find anything :good:
try Flashify app from the store :good:
Ok so "s-chassis" so being as persistent as I am:laugh:, I was able to find the stock recovery for VS98012B in another thread you can download it here:
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=193184686
Look at post #10
Then I used the dd method to flash the recovery, here it is if you forgot
adb push recovery_vs98012b.img /data/local/tmp/recovery_vs98012b.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery_vs98012b.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
I got back to the stock recovery but the android has a red exclamation mark on it not sure why but if you have any ideas let me know
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.
hello guys,
is there any custom frimeware for the galaxy grand prime sm-g532f ? i looked everywhere but can't find one.
i need one because there is no more space in my phone, the system took almost everything, 6.5go of the 8 availble, so i can't install big apps even with an sd card ! any solution ?
i was about to install a stock rom, but someone told me that it will take the same space as my current rom .
thank you.
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
sga-pingo said:
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
Click to expand...
Click to collapse
yes i have the same thought there will be no custom rom did you tried to install a stock rom ?
did you tried to install a stock rom ?
Click to expand...
Click to collapse
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
sga-pingo said:
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
Click to expand...
Click to collapse
thanks, i think i will try to root my phone, maybe it will work for me. my last hope :/
Please post your results, I am hopeless with this severely bloated device.
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
sga-pingo said:
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
Click to expand...
Click to collapse
i didn't have a lot of time these days to search for a working "rooting methode", so thank you very much.