ok guys this is my first time asking for help because i don't want to start all over again, i was on ics fb17/fb15 modem, running as my daily for about two days and i wanted to change the density like i did on gb, i don't remember what app it was because right after i changed it the phone rebooted to change it and got stuck at the galaxy s2 screen, so what im asking is if there's a way to command prompt into the phone and pull the build.prop and change the dpi back to stock and push it back so it can boot, also i suck at command prompt so if you can help, could you post exact commands for me to use, and yes Ive searched the forums and google and couldn't find anything that showed how to command prompt into it if it wasn't turned on. any help would be awsome
mypd1991 said:
ok guys this is my first time asking for help because i don't want to start all over again, i was on ics fb17/fb15 modem, running as my daily for about two days and i wanted to change the density like i did on gb, i don't remember what app it was because right after i changed it the phone rebooted to change it and got stuck at the galaxy s2 screen, so what im asking is if there's a way to command prompt into the phone and pull the build.prop and change the dpi back to stock and push it back so it can boot, also i suck at command prompt so if you can help, could you post exact commands for me to use, and yes Ive searched the forums and google and couldn't find anything that showed how to command prompt into it if it wasn't turned on. any help would be awsome
Click to expand...
Click to collapse
If you can get into recovery you can do command prompts from there. If you dont have a recovery I suggest download rogue with fB17 kernel baked in and then go to mounts and you can mount your system. I would start there first... Then we can deal with adb...
All you would have to look for is how to push a file using adb in a google search. Make sure you pull the build.prop file from your downloaded original rom/zip file to push it back to your phone
adb pull /system/build.prop
adb push build.prop /system/
Edit: You can also download adbcommander for your pc which does the same thing but through a program.
thank you so much, im just waiting on my sdk to update, kinda slow internet, and im guessing it should work, never thought about connecting it in recovery. thanks
mypd1991 said:
thank you so much, im just waiting on my sdk to update, kinda slow internet, and im guessing it should work, never thought about connecting it in recovery. thanks
Click to expand...
Click to collapse
I know this thread is a bit old, but I just found myself in the same boat... Just got my E4GT yesterday and been playing around. Decided to change DPI and after reboot i'm stuck on Samsung boot screen. I did have a recovery loaded, so I booted in pulled build.prop, changed it back and pushed back however still stuck. Did this fix your issue?
i just go into custom recovery and reflash rom without wipe n it boots back up
Sent from my SPH-D710 using XDA
elliwigy said:
i just go into custom recovery and reflash rom without wipe n it boots back up
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
This was my fix to get phone running again... But then how do we effectively update build.prop w/o causing it to stick at boot? First attempt was using ES File Explorer, enabled root and mounted system, modified only the DPI value in build.prop, saved, reboot. stuck at boot screen.
Update: Was looking at build.prop and noticed there are 2 lines containing DPI setting. I only updated the first line on my first attempt... This time I did adb pull from recovery, edited file, and adb push back. Then when i rebooted build.prop does not reflect my changes, still had default values.
Update:Tried using ES File Explorer again and made sure to update both lines, still get stuck at boot screen. Act's like phone is preventing any changes to it and locks up when it detects a change.
Ever get a fix for this??? I'm experiencing the exact same issue with my Galaxy s4 1337M on a TW lollipop Rom.
Related
Howdy everybody! I just got CM7 to boot for the first time on the Kindle Fire. As of right now, I believe the touch screen is off 90 degrees. I know there's a fix in the source code, I just forgot where it is but I'll look. It might actually be an edit to the build.prop. Pictures below:
http://i.imgur.com/SE4nx.jpg
http://i.imgur.com/8ZRCW.jpg
I'd really love to stay and chat, but I'm actually really late for work
More on this when I get off from work and before I gotta leave for school
12/4:
12/13
This ROM is obsolete; it was more of a proof of concept than an actual everyday ROM. It would suggest staying stock until ICS is ready and stable.
The ROM's update.zip
The KF's clockwork recovery to install files located under /sdcard/update.zip
The KF's stock recovery
md5sums
update.zip e0e8f8bb08318ef15c8afc042c2e9766 update.zip
updaterecovery.img 38eb5308439a6f1e256a4914ab06d508 updaterecovery.img
stockrecovery.img c4f028310bd112649c94be6a4171f652 stockrecovery.img
Make sure your battery is fully charged, rooted, you know your way around adb, and that your kindle fire actually connects to adb and works successfully before installing CM7. Installing CM7 will wipe your system, data, and cache, and I'm not responsible for any malfunctions :/ I've done this for versions 6.0 and 6.1, but I have not tested under 6.2
Copy the CM7 zip to the root of your sdcard, so it's /sdcard/update.zip, and copy the updaterecovery.img file to your sdcard so it's /sdcard/updaterecovery.img. For Clockwork, you will need two files to be present under /cache/recovery/ so copy these two files to your sdcard log last_log. You'll need to copy them to the root of the sdcard as well. Before proceeding, I highly recommend you go into adb and verify the md5sums of the two files you just put there. If you aren't familiar with this, you need to unmount your kindle from the PC, type:
adb shell
cd sdcard
md5sum update.zip and make sure the numbers generated after a few seconds match the numbers posted above
md5sum updaterecovery.img and again, make sure the numbers generated after a few seconds match the numbers posted above
If these numbers don't match, I wouldn't proceed as your file might be corrupt, and I would try again
Now we will need to copy these two log files to your cache partition under /cache/recovery so type
adb shell
cd cache
mkdir recovery
cd /
cp /sdcard/log /cache/recovery/
cp /sdcard/last_log /cache/recovery/
If your files are verified to be okay via the md5sums before, we can flash clockwork now, by typing
adb shell
dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Now, we can reboot recovery by typing "idme bootmode 0x5001"
If it says the bootmode has written, you can type reboot and it'll reboot
I install all of my zips without removing the usb plug from the computer or the kindle and I have never failed once, I don't think I've ever tried it without doing so, but if you don't wanna mess with success, don't remove the usb cord. I'm not saying anything bad will happen because I've never done it, but I'm just saying I'm batting 1.000 without removing the usb cord
Now that you're in clockwork, look below the menu to see if there are any error messages written in white. If you see one about something being read-only, that's fine. If it complains about log and last_log, you might've missed a step above. If you see an error that I haven't mentioned, and you would like to reflash the stock recovery and reboot like none of this ever happened, skip to the bottom.
About Clockwork: since we can't navigate to items in Clockwork, we have to bring the items to us. Basically what I did was I shifted the entries of Clockwork so the "Install update.zip from sdcard" was listed first, not the Reboot system now option. That way, we can just press OK (The power button) and it'll install the CM zip. I also changed it so you don't have to scroll all the way down to the "Yes" option to confirm install as I pushed that to the top also so we can just press OK. In the update.zip I included the wiping of system, data, and cache because we can't navigate to mounts and storage to wipe those things in Clockwork, so we have to do it automagically.
In the clockwork that I made for you, all you have to do is press the power button a bunch of times. There will be a point there you have to scroll down to "Yes", but you can't, that's fine, just press OK, even though it says "No" it will mimic you pressing Yes.
After you press the power button 3 or 4 times, it will being the installation. Give it a minute or so, it will install
After installation, we will need to reflash the stock recovery to your kindle. Type adb shell
mount sdcard
exit (this will bring you back to the non-shell command line)
then adb push /sbin/
So for me, (I use linux) I use adb push /home/jonathan/kf/stockrecovery.img /sbin/ **there's a space after .img and /sbin/**
Then type "dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery" it will say something about 16 megs written or something. Once that happens, type adb reboot or reboot and your kindle will reboot. Actually it will reboot twice. Give the initial boot a few minutes, and the CM7 boot logo will appear
Congrats Calvin!!! Awesome!
The only thing that tempers my excitement about this or CM9 is wondering what happens to Amazon's apps once we install a CM build of Android.
Will the Kindle still see Amazon and Visa Versa as a registered Kindle owner
Will the Amazon video app still be installable and usable (albeit we have to unroot?)
Re: Above...can CM be unrooted after installed?
Basically, I just want to know what I'm LOSING by going to CM on the Kindle Fire.
good job!
do the apps and wifi work?
tck9223 said:
good job!
do the apps and wifi work?
Click to expand...
Click to collapse
http://i.imgur.com/8ZRCW.jpg - it looks like
I wasn't able to test much out because the screen and the touch sensor aren't in sync. Basically the screen is facing one way and the sensors think the screen is oriented 90 degrees in another direction. There's a quick fix but I had to leave for work
I managed to open the wifi screen but couldn't click my ssid let alone type the password with the orientation/sensor hiccup
Sent from my DROID Pro using XDA App
rmagruder said:
The only thing that tempers my excitement about this or CM9 is wondering what happens to Amazon's apps once we install a CM build of Android.
Will the Kindle still see Amazon and Visa Versa as a registered Kindle owner
Will the Amazon video app still be installable and usable (albeit we have to unroot?)
Re: Above...can CM be unrooted after installed?
Basically, I just want to know what I'm LOSING by going to CM on the Kindle Fire.
Click to expand...
Click to collapse
I don't have all of the answers for sure but I think at this point no one really knows.
1. The device would no longer be registered as a Kindle if it is just stock CM. If you add the regular Kindle for Android app you wou still have access to kindle books but not other content.
2. The Amazon video app should work because it is reported as working on other unrooted devices. You should be able to unroot CM7(9) the same way that we currently unroot the KF. I suspect that it will not be long before we see a modified Kindle Video app that runs on rooted devices as I have noticed an increase in developer activity and interest in the device.
3. Yes
I too am concerned about these things as I have become very accustomed to instant video and all of the other features of the KF. I see many ways of having both. I suspect that once CM is fully operational we will have a zip that we can flash in recovery to add all of the Amazon apps the same way we do with gapps.
Suprising to see a ROM before a recovery.
Sent from my SPH-D710 using xda premium
Lol we have recovery. It's just ineffective
Sent from my DROID Pro using XDA App
pyrostic said:
Suprising to see a ROM before a recovery.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Very surprising but the recovery might be released before the ROM
The Fire is my first Android device and I have been following the XDA forums closely because this kind of hacking and tweaking is just WAY to cool.
Congrats on the CM7 boot. Can't wait to see more!
Got a donate button? I'll throw in for the hard work! Would love working CM7 or 9 on this guy.
SikYou said:
Very surprising but the recovery might be released before the ROM
Click to expand...
Click to collapse
You know something about TWRP I don't?
Sent from my SPH-D710 using xda premium
I know when its released loads of Rom development will follow.
pyrostic said:
You know something about TWRP I don't?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Probably not. I know that there is a working build though and that it has been said to be working great. I know there are still some hurdles but the guys are working hard
Sent from my Kindle Fire using Tapatalk
SikYou said:
Probably not. I know that there is a working build though and that it has been said to be working great. I know there are still some hurdles but the guys are working hard
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Talking about TWRP? if so what hurdles?
Sent from my SPH-D710 using xda premium
Well I flashed cm with clockwork. I'll post a zip and instructions later
Sent from my DROID Pro using XDA App
JackpotClavin said:
http://i.imgur.com/8ZRCW.jpg
Click to expand...
Click to collapse
Great news.
But I think the biggest shocker is why do you have your wifi set to WEP?
pyrostic said:
Talking about TWRP? if so what hurdles?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yes TWRP. I am not 100% sure what is holding up the release. Agrabren has TWRP working on the KF but says that it may be a week or 2 until it is ready for release, he is the only one that knows for sure still needs to be done. I think 1 problem is lack of an easy way to boot in to recovery. Either way, looks like we aren't far off.
Sent from my Kindle Fire using Tapatalk
JackpotClavin said:
Howdy everybody! I just got CM7 to boot for the first time on the Kindle Fire. As of right now, I believe the touch screen is off 90 degrees. I know there's a fix in the source code, I just forgot where it is but I'll look. It might actually be an edit to the build.prop. Pictures below:
http://i.imgur.com/SE4nx.jpg
http://i.imgur.com/8ZRCW.jpg
I'd really love to stay and chat, but I'm actually really late for work
More on this when I get off from work and before I gotta leave for school
Click to expand...
Click to collapse
Congrats! Do you have a github repository somewhere that you've got your code committed that we can look at? I do CM7 for the Samsung phones (Galaxy S and Galaxy SII), and so I'm interested in putting Ice Cream Sandwich on the Fire but haven't got around to doing anything on my Kindle because I've been busy the ICS for the phones. Starting with what you've got would be a good start and then I can try to put ICS on it.
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
And actually it might even be a safer approach to revert to stock from a stock like rom http://forum.xda-developers.com/showthread.php?t=1439916
Bricked beyond all recognition baby!
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
putney1477 said:
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
Click to expand...
Click to collapse
Even if you want to go back to pure stock, keeping/reinstalling both TWRP and FFF are the safest and smartest things to do.
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
putney1477 said:
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
tamaker said:
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
Click to expand...
Click to collapse
I have the same problem, but my battery was 100% when flashing back. Is this good night for the kindle then?
It boots in to the 6.2.2 software, but these errors pop up and force close then eventually does a restart. Dammit!
putney1477 said:
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Dasanko said:
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Click to expand...
Click to collapse
oh ok, thanks
Just a side note after restoring to stock you need to then perform a factory restore as well which will wipe your sd card if all goes well it should smooth out from there
Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
putney1477 said:
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
Click to expand...
Click to collapse
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Dasanko said:
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Click to expand...
Click to collapse
OMG! I can't thank you enought for taking the time to answer all of my questions!!! It worked!!!! I am back to stock! (I had no doubt, thanks to you!) THANK YOU!!!
Heather
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Try flashing the stock tar in odin if nothing else works.
DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok
I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol
fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha
So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop. I tried all the methods I could find on xda but none worked. I then started reading all the way through threads and found the fix... wish they would update the original posts... so for those in this same predicament, here is how I fixed it so you don't have to read through everything.
so the FULL ADB method code looks like this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
exit
adb reboot
I of course take no responsibility if this doesn't work for you. I got the original and extra code in this thread http://forum.xda-developers.com/showthread.php?t=2451696 and all true credit goes to them. I'm simply putting ALL the information in the one original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
kuwlij said:
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
Click to expand...
Click to collapse
tried this didn't work? even wiped the data still have the icon.... Any other suggestions?
vegasdavek said:
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
Click to expand...
Click to collapse
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
This is almost an exact repost of the other bootloop fix.
TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Yup. This is a repost only. I have seen couple of Guides here in G2's thread.
Sent from my LG-D802 using XDA Premium 4 mobile app
TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Agreed, which is why I said that the other thread is where I found the fix... but the original post in that thread didn't actually offer a fix when I got stuck in the loop. As a result I spent a lot of time trying other attempts to fix as well as combing through threads before finally finding the extra line of code to make it work.
So I posted a new thread so that someone else doesn't have to waste their time like I did trying to find a fix.
DooLocsta said:
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
Click to expand...
Click to collapse
I'm using this rom currently: http://forum.xda-developers.com/showthread.php?t=2595586 as I too need the WiFi Calling feature.
If you are on a T-mobile based rom, the way to 'freeze' the update is different than the others.
T-mobile roms use 'Google Services Framework' for the update, and obviously you can't freeze that app.
So, what you do is d/l a program called 'Autorun Manager'. Then inside that program, scroll down to 'Google Services Framework' and disable 1 receiver.
The one you want to disable is called 'com.google.gsf.update.SytemUpdateService$Receiver' Just disable that (by unchecking it) and then reboot. You will not receive a notification to update ever again.
Also, go into the folder /cache and delete the FOTA d/l. You will need R/W permissions in the root directory to do this. So use whichever file manager you prefer for that.
The FOTA d/l is easy to spot, it's a 150mb approximately zip file with a bunch of chars and should be the only file in that directory. There are a few folders as well, but, ignore them and just delete the 1 file.
I'm in the same situation - reverted back to stock rooted with twrp recovery and now boot back to recovery. I haven's used adb much, but do know how to open the cmd window in the adb directory on my computer and it appears I'm connected to my d800. However, when I run the adb devices command I see the device code and recovery listed. When I type the first line of the code in the first post, adb shell, I get ~ # ←[6n and can't type in any additional commands.
Am I missing a step - or just not understanding the process??
UPDATE - Nevermind - I just typed in the command dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota using TWRP's Terminal Command and the phone booted right up to Clean Rom.
Thanks vegasdavek for your repost on this fix!
vegasdavek said:
So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop...
original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
Click to expand...
Click to collapse
Thanks, found this now, only after I already fixed my issue, but this is useful. Perhaps you should also update it to reflect it can be done with the Terminal in TWRP..
guys im in deep trouble here. my phone got softbricked after i made changes in build.prop(just changed dpi) using some text editor. after saving the file and restarting the phone. its not turning on, just blue and green led flashing. tried to use the pc suite, and flash tool 2014, but still no success. i can still go to download mode though. hope someone help me here
Sent from my SM-T705 using Tapatalk 2
deejay6901 said:
guys im in deep trouble here. my phone got softbricked after i made changes in build.prop(just changed dpi) using some text editor. after saving the file and restarting the phone. its not turning on, just blue and green led flashing. tried to use the pc suite, and flash tool 2014, but still no success. i can still go to download mode though. hope someone help me here
Sent from my SM-T705 using Tapatalk 2
Click to expand...
Click to collapse
Flash Rom using Normal instead of CSE? Next time either read more threads or use a proper editor or even better: a pc to edit build.prop.
Otherwise you can try to adb push original build.prop to your phone but flashing Rom is much easier imho.
Pfeffernuss said:
Flash Rom using Normal instead of CSE? Next time either read more threads or use a proper editor or even better: a pc to edit build.prop.
Otherwise you can try to adb push original build.prop to your phone but flashing Rom is much easier imho.
Click to expand...
Click to collapse
i wanted to try and flash a build.prop but dont know how. ive already tried flashing kdz file but didnt work out. actually im not new to this as ive been rooting my phone since s2 days, even when i bought this amazing phone i rooted it right away. but after i update it to 10i, i tried rooting back which worked fine, however when i tried editing the build.prop thsts where this problem comes out.
Sent from my SM-T705 using Tapatalk 2
You didn't set the permissions right for the prop file, that's why it's stuck in a bootloop.
Permissions are suppose to be rw r r.
Also, modifying via 920 Text Editor or via your PC, then load it back into the phone.
Could be the editor used did not handle the whole very large build.prop file and truncated when you saved it.
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=2799647
Read it. You might get Download Fail can not restart to download mode a few times. Keep trying, use different usb ports restart computer, try again, restart phone to download mode. I must have got that message 50 times then all of a sudden it worked. Its a pain but see how it goes. There is another way but it is a pain and involves lots of setup.
Check post 202-203:
without flash back after bootloop. (for next time)
http://forum.xda-developers.com/lg-...s-free-ram-t2825693/post55094520#post55094520
A warring about build.prop without the right app. (from what dorimanx said ! )
http://forum.xda-developers.com/showpost.php?p=54970011&postcount=171
to find & download your right and last Ver. rom stock by your imei
http://forum.xda-developers.com/showthread.php?t=2683691
If you chance settings on Build.prop to worng setings you can and will have bootloop.
here are what in that post said about DPI and more...
#Best dpi for G3
#default value 640
ro.sf.lcd_density=560
Source:
http://forum.xda-developers.com/lg-g3/general/guide-build-prop-tweaks-free-ram-t2825693
http://forum.xda-developers.com/showthread.php?t=2781043
App fot DPI Ch...
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
or
https://play.google.com/store/apps/details?id=com.theSushi.dpichanger
scarecrow2012 said:
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=2799647
Read it. You might get Download Fail can not restart to download mode a few times. Keep trying, use different usb ports restart computer, try again, restart phone to download mode. I must have got that message 50 times then all of a sudden it worked. Its a pain but see how it goes. There is another way but it is a pain and involves lots of setup.
Click to expand...
Click to collapse
yes this did worked for me. i tried to chaged port then suddenly firmware update did run. and now my phone has resurrected back from the dead...
now... back to modding!! hahaha...
Sent from my LG-D855 using Tapatalk 2
deejay6901 said:
yes this did worked for me. i tried to chaged port then suddenly firmware update did run. and now my phone has resurrected back from the dead...
now... back to modding!! hahaha...
Sent from my LG-D855 using Tapatalk 2
Click to expand...
Click to collapse
Congrats, all the best with the modding.