Related
Hi all!
I did try searching, might be too simple...
New to Android, etc...
Windows and Toshiba taught me to always download original files and archive them for later recovery, drivers, etc... to factory recovery years later when needed.
Now with this...
I think I was at JRN84D (4.1) when purchased on vacation, took OTA update to JRO03D (4.1.1).
At Google, ONLY JRO03D is available.
? Should I hunt around to find and archive JRN84D (or ask for someone else's archive PM) or will JRO03D always be THE factory recover baseline for this device?
?If they replace JRO03D with something else, will those always be then considered the factory baseline? (Or should I keep a progression of images?)
?I think since this is flashed, that my OE file (JR84D) is truly gone forever, since JRO03 is flashed 'over' it, and I can never really factory recover to 'out of the box' state - am I right?
(Trying to get my ducks in a row to start trying Mskip's package...)
THANKS
As long as you have the net Mskips tool will download a stock rom and flash it for you anyway
Sent from my Nexus 7 using Tapatalk 2
ROM/ DISK Drive devices.Failure rate .
There is a huge difference in A Tablet os then the tradition installation of windows. Windows is a compiled bunch of software running on a Disk drive.. High Failure rate.
Android Tablet phone/ devices. These are firmware running on a non destructible ROM CHIP. if you are totally stock..and never change that. There is a pre made so to speak backup built in.. This will restore your device to its original state.
You can download the latest firmware os / kernel from gogle as i see you have found already. Be SURE you have and know how to use the tools to flash the software in case of a non boot situation.. I would not count on the install tools mentions above.. FASTBOOT ADB AND BOOT-LOADER COMMANDS .... If you really want to learn about android and understand arm devices more . Lots of information with a google search..
So what im saying is a Un rooted tablet have a very low almost near software error rate. (A QUICK RESTORE WILL FIX EASLY)
If you are not root and you mess up your tablet simple fix.
If you root your tablet and install a custom recovery.. Then you need to save the tools to install the recovery the recovery files. The Boot-Loader files and the ROM. YOU are using or want to use.. Could be stock ROM CUSTOM ROM. if you use a custom kernel you need this as well.
You should also first boot into the CUSTOM Recovery MADE A NANDROD BACKUP... This will be your ticket to restore the device quickly and easy.
I know this is alot of vague information but it kinda touches what your asking..
Good luck .. Guys feel free to fill in the blanks and correct my mistakes.. OOPS Erica makes no mistakes right .. hehe
THX all - I've , let's see - unlocked, rooted, flashed a new rom, restored 'factory' rom, unrooted and relocked - whew!
I think there is a real problem with terminology for OE roms - both by users and the OE. My device says factory or factory state in it somewhere - but that is clearly not what it means. It means current factory or something like that - and that it will never be back to the out-of-the-box factory state. Apparently, I can only ever get back to the cleared-of-user, current 'factory' state.
Anyway, I've a recovery method and the current rom stored for the future.
Is there a site that store earlier roms?
Hi everyone, Pleasure to be part of this forum. Yesterday I received my Google Edition GT-i9505G. I originally came from an M919, but I liked the port of stock android on the m919 so much that I splurged for this phone!
I'm having a problem with the stock recovery not being able to wipe the Cache partition. The recovery will show the little green android on the bottom, and goes between "error" and "no command" when you start the recovery. When you try to wipe the cache, it says "error" with the dead android then reboots.
I have been back and forth with tech support today, and before i ask for a replacement and risk getting charged for another device, I want to know if anyone else has this issue with their new phone. If the .tar files for the original firmware existed, I would of tried flashing through odin.
Phone is STOCK STOCK. I like it this way thats why I paid so much upfront for It LOL.
Please anyone else with a GS4 Google Edition, try wiping cache partition from the recovery and let me know!
Mods, if this can be moved to another section better suited please do!
Many thanks!
Afternoon Bump! There's gotta be more GT-I9505G users
BURRITO_LTE said:
Afternoon Bump! There's gotta be more GT-I9505G users
Click to expand...
Click to collapse
Flash a non-stock Recovery, its the only way to get those capabilities. I suggest PhilZ Touch recovery here:
http://forum.xda-developers.com/showthread.php?t=2281367
As to the best of my understanding the I9505G is identical to the I9505 except the main system partition. But that shouldnt be an issue for Recovery.
AMDPOWERFIST said:
Flash a non-stock Recovery, its the only way to get those capabilities. I suggest PhilZ Touch recovery here:
http://forum.xda-developers.com/showthread.php?t=2281367
As to the best of my understanding the I9505G is identical to the I9505 except the main system partition. But that shouldnt be an issue for Recovery.
Click to expand...
Click to collapse
So you say that its impossible to wipe cache partition on stock recovery? I recall this was possible on my note 2, worked just fine. I tried a tmobile s4 (m919) today and it did it successfully.
I don't want to mess with the stock configuration yet until i get bored, or support is dropped one day. At this point I'm starting to regret the purchase and actually was more satisfied with a m919 and the GE 4.2.2 rom.
Thanks for your insight :good:t. If any other GT-i9505G owners want to try to wipe cache with stock recovery, please chime in!
BURRITO_LTE said:
So you say that its impossible to wipe cache partition on stock recovery? I recall this was possible on my note 2, worked just fine. I tried a tmobile s4 (m919) today and it did it successfully.
I don't want to mess with the stock configuration yet until i get bored, or support is dropped one day. At this point I'm starting to regret the purchase and actually was more satisfied with a m919 and the GE 4.2.2 rom.
Thanks for your insight :good:t. If any other GT-i9505G owners want to try to wipe cache with stock recovery, please chime in!
Click to expand...
Click to collapse
Same thing happened to me when I restored to official firmware from custom ROM on a i9505 I've read it happening to a few other people on here and no ones been able to explain it so far
all I9505 also has this problem, problem with Samsung stock revory i think
Sent from my GT-P6800 using xda app-developers app
Must be allergic to custom recoveries, especially with them having so much more functionality and options and other useless stuff like that.
norml said:
Must be allergic to custom recoveries, especially with them having so much more functionality and options and other useless stuff like that.
Click to expand...
Click to collapse
well, not really. I had TWRP on my tmobile GS4, Of course it has more functionality. The sole reason i got the i9505G is because its perfect out of the box for me. No need to tweak it. Lame i know, but i was always peeved about the small bugs on the custom roms.
Hopefully samsung and google update this baby for a while, and if not, then I just spent 650 bucks outright for no special reason.:silly: (for me anyways)
I'm just peeved that the stock recovery wont clear the cache. Kind of like buying a brand new car, then noticing that the dome light is burnt. Of course you want it fixed. Lol hope you understand.
Up till now, thank you for the responses, I have found some videos on youtube of different variants of the S4 entering stock recovery. Some do the error/no command thing, others don't. There is one video of a i9505 failing to wipe the cache too (my main concern). Google offered to replace it, but before i risk getting a replacement with the same "problem" or even worse, an iffy SAMOLED (been there done that) i just want some insight. If its all phones then i will just wait it out, If its a few phones, then I will try a replacement. Cant find the official 4.2.2 firmware yeT!
Thank you for the responses guys.:good:
So ur not going to even root it? Why buy a car, if you can't even get under the hood?
norml said:
So ur not going to even root it? Why buy a car, if you can't even get under the hood?
Click to expand...
Click to collapse
hahaha good one! I actually do like to get under the hood of my car. but right now this phone to me is just a reliable daily driver, why mess with it? Im happy as is.
Il keep this thread up for a day or two more then il test a replacement. If the same issue arises, then i will update and end of story.
Thanks guys for your input. Im just a relative noob in this area. I know the very basics, but im not the type that tests out different roms all the time unless the phone is orphaned by the OEM or, intense bloatware.
:good:
I rooted my i9505G (google edition) by booting into the i9505 CWM recovery (NOT flashing it just doing adb boot (recoveryfilename)
Applied supersu zip file - BUT I could not for the life of me get the external SD card or local storage to mount.
This i9505G has such a different partiton/file system vs. touch wiz variants that at some point it WILL need it's own CWM recovery version.
Suggestion is to use sideload to push any root enabling zip's (select install zip, install zip via sideload, then on pc/mac adb sideload (zipfilename)
PS: I did a fastboot oem unlock on my mac prior to doing the above; not sure if adb boot is protected without this.
Just chiming in to say mine gives me an error when I try to wipe cache with stock recovery too.
jpculp said:
Just chiming in to say mine gives me an error when I try to wipe cache with stock recovery too.
Click to expand...
Click to collapse
Same here with i9505
Thank you so much for the reply guys. I guess if this is as common as i think it is, its not worth it to deal with google for a replacement phone which will most likely do the same thing. I'm just crossing my fingers official odin flasheable firmware gets leaked for these phones so I can feel more at ease flashing custom roms/recovery when they become available.
I appreciate the responses!
Thank you
have this problem on my I9500 too
when wipe cache partition the command line didn't say anything and only show image of dead android with red "X" mark and reboot
in my old phone the command line say something like "wiping" "processing" "wipe complete /succes"
NPS_CA said:
I rooted my i9505G (google edition) by booting into the i9505 CWM recovery (NOT flashing it just doing adb boot (recoveryfilename)
Applied supersu zip file - BUT I could not for the life of me get the external SD card or local storage to mount.
This i9505G has such a different partiton/file system vs. touch wiz variants that at some point it WILL need it's own CWM recovery version.
Suggestion is to use sideload to push any root enabling zip's (select install zip, install zip via sideload, then on pc/mac adb sideload (zipfilename)
PS: I did a fastboot oem unlock on my mac prior to doing the above; not sure if adb boot is protected without this.
Click to expand...
Click to collapse
I used the same method ...
fastboot oem unlock
... go through set up ...
adb reboot bootloader
fastboot boot recovery-clockwork-touch.img
After the fastboot boot command I get:
Code:
cannot load 'recovery-clockwork-touch.img': No error
My lock state is definitely "unlocked" and everything else is stock 9505G as it came.
Quick update
Well, Quick update.
I received the replacement phone, and this one did the dame thing. Error. Plus the bezel came all scuffed up. Now gotta go fight with google to keep my original one.....
Well If anyone is in doubt, most likely all/most 9505G's are like this and have a buggy stock recovery.
BURRITO_LTE said:
Well, Quick update.
I received the replacement phone, and this one did the dame thing. Error. Plus the bezel came all scuffed up. Now gotta go fight with google to keep my original one.....
Well If anyone is in doubt, most likely all/most 9505G's are like this and have a buggy stock recovery.
Click to expand...
Click to collapse
I have an SCH 1545 and have the exact same issue running stock 4.22
Same situation here withmy stock s4 I9500 in india.my s4 also shows error and reboot aftet that during wipe cache partition.
Sent from my GT-I9500 using XDA Premium 4 mobile app
I called Verizon, while they acknowledged the problem was rampant, they didn't have a clue as to how to fix it.
It must be another samsung idiosyncrasy that doesn't jive with 4.22..is anyone having this issue that's running something besides 4.22?
Alan - We all stand on the shoulders of Giants, so try not to **** on them.
As the title says I have an International GT_I9500 unlocked
Until now I was always able to install any custom rom I wanted , no problem, just wipe and install and away we went.
Now with KitKat, I AM COMPLETELY UNABLE TO INSTALL ANY OF THE CUSTOM ROMS FOR 4.4.2 -0 NONE WORKS. I can't believe i am jinxed.
I wiped everything, cache, dalvik, system and internal and also did a full wipe - NOTHING WORKED, There are 3 custom roms for 4.4.2 so far and NONE = NOT A SINGLE ONE WANTS TO INSTALL.
I downloaded one of Samsung original 4.4.2 firmware and using Odin I WAS ABLE TO INSTALL AND MAKE IT WORK, yet after doing this, I tried to install any of the 3 customs roms and BOOM, COMPLETE FAILURE
Can anyone help PLEASE GUYS, I feel like BROOMHILDA LONE PERSON WITH A CLOUD ONLY ON MY HEAD
I am curious as to why this is happening
maybe its a i9505 or i9506 rom
provide the Odin messages here.
custom roms failure, huh?
spamtrash said:
provide the Odin messages here.
Click to expand...
Click to collapse
I loaded the custom roms via recovery, not via odin,
so i go into recovery mode via TeamWin, wipe everything and load the custom rom, message says "successful" and i reboot system, that's it
the phone hangs into one of the boot animations and never finishes, left it for longer than 30 minutes, all of them , nothing loads.
go back the same custom roms but with android 4.3 and first shot, loads fine, all of them, same ones that won't load the 4.4.2 load the 4.3
most custom roms load via recovery not odin -
last try was load samsung original firmware 4.4.2 via download Odin, then root then install teamwin recovery. - worked fine
now removed it and reinstalled Thor 4.3 (thor 4.4.2 doesn't work) but tomorrow i'll wipe it and reinstall the samsung 4.4.2 unless you have an idea
*i hope)
sorry about the capitals - NO IT IS AN EXYNOS UNLOCKED GT-I9500 - almost a year after playing with nova settings, xposed and about a dozen custom roms, i THINK i know it's a 9500 - skip the silly suggestions - we're all noobs but not necessarily all boobs
thanks for your help - appreciated if we can solve it
custom roms failure, huh?
KingOfDope said:
maybe its a i9505 or i9506 rom
Click to expand...
Click to collapse
roms were downloaded exclusively from GT=I9500 AREA -
i don't go anywhere else because i know beforehand that they won't work - so why bother
thanks for your suggestion but obviously out of context - i don't live in the US in addition
Maybe wrong recovery ¿?
funny 4.4.2 roms
robertostorm said:
Maybe wrong recovery ¿?
Click to expand...
Click to collapse
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
exlaval said:
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
Click to expand...
Click to collapse
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
custom roms failure, huh?
robertostorm said:
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
Click to expand...
Click to collapse
as i said in a previous message - i used odin in download mode and flashed an original samsung 4.4.2 and it worked, i rooted and reinstalled teamwin
AFTER ALL THIS I tried to install one of the 4.4.2 custom roms - IT FAILED CONSISTENTLY - BY THIS I MEAN ALL ROMS DIED AT BOOTANIMATIONS - AND ALL FAILED TO START
thanks so much
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
custom roms failure, huh?
ayedarts said:
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
Click to expand...
Click to collapse
just downloaded cwm version 6.0.4.6 installed via recovery. launched recovery installed latest wanamlite for 4.4.2 - message was "installed successfully" please reboot
i rebooted and for the last 15 minutes all i have is a BIG SAMSUNG on the screen - nothing beyond
just another hitch with kitkat - i have a SONY XPERIA Z TABLET with wifi and sim - a couple of weeks ago i rooted it but the cwm version is not good because it's on the vertical side and you cannot see the bottom of the menu so it's useless - anyhow. i rooted it and left it at that.
i got notice from sony that a new os version (kitkat) was ready for install - so I just told the tablet to start - and the os install screwed the tablet,
there was no way to reload and it completely deleted the memory , it went to sony to reload - so i have a big hunch there is something not right somewhere -
anyway the phone still has the SAMSUNG and it ain't going anywhere while i am writing all this
very discouraging = sure as heck i ain't buying no more galaxys of any sort, i was ready to preorder the s5 at 455british pound, unlocked - but since this i am dropping samsung, i like very very much the xperia tablet it's faster than the s4 so perhaps i'll jump to the sony xperia fone and bbye korea
maybe i9505 rom
custom roms failure, huh?
i know you're trying to help - but if you read all the previous (long and boring) messages - there's no mistakes, there's no 9505
ALL THE ROMS I DOWNLOAD AND USE - ALL OF THEM WITHOUT EXCEPTION come for the i9500 development area, I DON'T BOTHER WITH
9505 - MOSTLY BECAUSE I DON'T HAVE A 9505
UPDATE - today after loading the latest cwm recovery i got lucky to be able to load ONE - READ IT - ONE CUSTOM ROM ( rom from HASAN)
this is the very only that i got to work, the other two just refuse to finish the boot - i don't know where they freeze.
even the wanamlite custom rom for 4.4.2 freezes - this is really annoying and a puzzle - this is my fourth samsung fone and never ever did i
find the bug that freeze everything. I hope that some of the other developers will come up with new kitkat versions for the 9500 and see if the bug persists or not -
any help will absolutely be appreciated, guys, some sort of boot log that can help pinpoint,
thanks again
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
custom roms failure, huh?
pinktheater said:
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
Click to expand...
Click to collapse
-------------------------------------------------------
First - The capitals I used were ONLY to emphasize certain aspects and not intended as screaming, which is the usual sense - That was not my intention,
Second - I have being using Samsung for the last 7 years, I was not intending to leave until I hit this brick and further I nearly went to Clove, UK (where I usually pre-ordered my last 3 Galaxy's - months ahead of delivery) so thumping me by saying I am looking for an excuse to dump Samsung, is way off base, so much so, that if that indeed was my intention, why for all heavens would i bother to find a solution, and waste so much time and effort to make it work
Third - I have being as polite as any person can be, with or without, this hitch, don't judge, about being angry or not, you don't know me well enough to know the difference, just stick to the point in question without getting personal.
Fourth - What I have described is EXACTLY to a tee what is happening to me, what happened to YOU , is IRRELEVANT, you may be one of the lucky ones who has no issues installing the roms in questions. so unless you do have a suggestion as to finding the reason the fone loops on boot, skip what you did or didn't do, they are IRRELEVANT, because they don't provide a solution.
Fifth - If you read my descriptions you will notice the many times I installed customs roms on the many galaxy's and Note's I have/had.That ought to clue you that i know a basic way on how to do the installations (Odin, recovery, teamwin. cmw,) you name it I've done it, and i've unbricked more than once my fones. so yes i do know how to use Odin
Sixth - For some reason I was able to install the "HASSAN" rom (the ONLY and ONLY) 4.4.2 custom that worked. the others they just won't, PERIOD
So if you have a technical solution as to how to get a log of the looping so we can tell exactly at what point the fone loops. or some other technical solutions, please let me know them asap I am dying to see my fone with a custom 4.4.2,
Seventh - Yes I am extremely disappointed that the S5 is just not fantastic enough to lay 455GBP to pre-order. there are a few more advances but it is "ALMOST" good = the bezel didn't disappear - the 2K display isn't there - the sharper casing is still missing - the better battery is still not there - the wireless charging - To have 2000 horse power engine under the hood of a beat up VW beatle. doesn't make you good looking enough to go cruising on a saturday nite and brag about your "car" -
BTW = I am absolutely no fan of the Iphone (yuk) nor of Sony (which is as restricted as apple)
Can you help solve my issue - thanks
Hello guys.
I would like to ask you for help with my bricked Homecare. I apparently cocked up the flashing process and now I don't know, how to proceed.
What I did:
At first I used the Russian (translated) version of supertool designated for Homecare Note 7. But the process wasn't 100 % successful. The bootloader has been unlocked, CWM recovery has been flashed, ROM 4.3 has been flashed. The tablet was able to boot, but it always froze after a few minutes of operation. Most probably there was a wrong boot flashed. No idea.
So, I checked the forums and RootJnky's videos and decided to use CWM to flash a deodex 4.3 stock ROM.
Flash process was successful, but after restart the tablet remains in boot-loop.
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB.
Right now the only status except a boot-loop is the APX mode. Is there still a chance how to unbrick the tablet???
Thanks for any advice.
Jaro
jardam.cz said:
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB...Jaro
Click to expand...
Click to collapse
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
e8hffff said:
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
Click to expand...
Click to collapse
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
hacktrix2006 said:
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
Click to expand...
Click to collapse
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
jardam.cz said:
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
Click to expand...
Click to collapse
The bootanimation.zip is in /lbh partition under media. Should be a easy enough to copy and paste in if not then i will have a look for a way of doing it without flashing all of it again.
Docs on Homecare Fly One rom update
Hi jardam.cz AND hacktrix2006
I see you guys have a working method to update the Homecare Fly One - do you have any documentation on how to root and update the rom for this model? Jardam mentioned a Russian rom, but it caused problems. I really don't want to brick this, as I live and breathe with this tablet every day! But I can't stand the limitations of no root.
Almost all the YouTube videos show EVGA solutions, and lots of people have Homecare Fly One problems - what's the solution please?
They are all the same base nvidia model which is p1640 the lbh partition is wrote when flashing via apx mode which can be risky. However there is a twrp recovery for our device and a stock 4.4.2 image from tom you can use to flash a generic version if the os.
Some basics - About bootloader, kernel, recovery, rom, /system and some other partitions.
There are many noobs out there and sometimes even I am one. Two days ago @Closed Force asked me, where I know my stuff from and why things are like they are... So I finally decided to write this little guide about how Android devices basically work and what are the special things about our G2.
If you find wrong facts or any other mistakes (grammatical, language, contentwise), please bear with me. That's how I read it in the forums. And of course not everything written on XDA is correct. So please tell me by PM, or by posting in this thread if you have additions, corrections or any other concerns about this OP.
Where I got to know all this stuff? Reading, reading, reading. I first started modding my old HTC desire like 4 years ago. Since then and even before I'm reading. Mainly here on XDA but also on some german forums and wikis. It might have taken me easily 200 hours or more. So the only way to learn for a newbie (and everyone else too) is reading.
Personally I own a D802 variant. I know about some things that were different in details for the US variants, but things should be right as they are.
Finally thanks to
@d00lz for some extra research/additions and a quick read through.
@Art Vanderlay for some additions.
So let's get started:
When you press the power button, your device will load the Bootloader. The Bootloader afterwards wil load either the Recovery Image (recovery.img), the Kernel (boot.img) or the Download Mode Bootloader (laf.img), depending on the keys you press. At the moment there are three different bootloaders; The Jellybean one, the KitKat one, and the new Lollipop one. Not one of these Bootloaders can be unlocked yet, so there are workarounds which allow us to boot custom ROMs (specifically Kernels, but more about that later) and custom Recoverys. At the beginning there was the Jellybean Bootloader. The Developers (sorry, I don't know which ones) found out how to get around the locked Bootloader pretty early. They called this workaround Loki. It's intergrated into nearly every ROM except the ones which require the KitKat Bootloader (but that's usually not the reason they don't support the JellyBean one). Anyways, soon the KitKat update came and so did the new KitKat Bootloader. Sadly, LG patched the Loki exploit with this new update. However, the Developers found a new way to get the Bootloader booting files which weren't signed by LG. They called this workaround Bump. Bump basically imitates the LG signature so the bootloader thinks this file was really signed by LG. Obviously this workaround works with the JellyBean Bootloader too. In the Lollipop Bootloader this exploit has been closed and no one knows how to get around the new Bootloader, yet. In conclusion to Bootloaders, as long you have a working Bootloader, your device is not dead. You can usually recover it in some way.
The G2 has about 30 partitions (for a more detailed explanation, look here, thanks @d00lz). Each partition has its own purpose. One of them is the Recovery partition. Imagine: A Recovery partiton and a working Bootloader are everything you need to keep your phone working. It's kind of an Operating System in itself, completely independent from Android or anything else stored on your Mobile. The great thing about the Recovery partition is that it's so small that it can be run directly in the RAM. This means it's capable of modifing EVERY goddamn partition on your Mobile, including the Bootloader and the Recovery partition itself (means you can flash a new recovery.zip in your current recovery). Attention: if you are using the Recovery with a 4.4 KitKat Bootloader, it needs to be a Bumped Recovery. If it isn't bumped the Bootloader realizes that the Recovery is not genuine and generates a "Secure Boot Error".
Same thing goes for the Kernel. The Kernel is located in your /boot partition (found gzipped inside your boot.img) and is loaded by the Bootloader when you only press the Power Button and you let your Mobile boot normally. This is the reason why your Kernel also needs to be Bumped if you want to get your system booting on a KitKat Bootloader. When 4.4 KitKat came out, most Developers switched over to using LG's 4.4 KitKat sources for their projects. After a while it was realized that 4.2 JellyBean sources were a lot more reliable for AOSP baed ROMs. This is why most AOSP ROMs use the 4.2 JellyBean Bootloader and the 4.2 JellyBean Kernel sources while Stock based ROMs use the 4.4 KiKat Bootloader and 4.4 KitKat Kernel. There are different Kernels for AOSP ROMs and for Stock based ROMs. This is because Stock Kernels support some ROM functionalities that AOSP ROMs don't have, for example; Knock Code. (Note: Knock Code isn't open source, which is also another big reason why it isn't available for AOSP ROMs.) So there are huge differences between Stock and AOSP based ROMs/Kernels. The Kernel (without factoring in the AOSP and Stock issue) can be switch at anytime you want.
Now about the /data partition... All your personal stuff, including Apps, System Settings, App Data and so on will be stored there. The reason why you should clear it every time you change the ROM is that there are many variables set by the ROM you are coming from. Your current ROM may have some tweaks the new one doesn't have which means the new ROM doesn't know how to handle them which leads to crashes and instability.
Now let's get to the ROM... Having a 4.2 JellyBean Bootloader and a 4.2 JellyBean Kernel doesn't mean the top layer has to be 4.2 too. Most of the AOSP based ROMs are based on Googles KitKat or Lollipop sources. And this is true KitKat or Lollipop, with all its functionalities. Those huge version differences cause some problems in development. No wonder some things do not work properly today, but it's still the best working combination at the moment. It's kind of a wonder how it works as it is, but let's be happy with it. I'm very curious how AOSP ROMs with Lollipop Kernel sources will work. Your ROM and your entire existing Operating System is found in the /system partition. This is why it's the main partition which is modified while flashing. Which partitions will be modified and (how) is written in the updater-script file of the file you're going to flash. Theoretically, running a updater-script of a ROM which changes the Bootloader (/aboot partition) can brick your device. That's also the reason why you should only flash stuff made for your device only!
As already said an updaterscript can modify every partition through the recovery. All ROMs bring their own kernel, so you basically don't have to care about it, except you want to use a non-bumped ROM (with kernel) together with the KitKat bootloader.
Finally something about the baseband/modem (these terms are interchangeable). I noticed that the Developers or rather the Original Posters sometimes don't know which baseband the user should use with the ROM. In earlier days the wrong baseband could make the ROM bootloop. Today most ROMs work with most basebands. It's obviously best if you stay on the one you currently are on and just flash another one if something doesn't work (auto-rotation for example). The baseband can be flashed at any time and is on it's own partition.
Okay Download Mode time. It's part of the laf partition (laf.img). This partition is used by LG and it's PC software to recover the phone and bring it back to Stock. It's a partition in itself, but not completely independent of the Bootloader. It's because of this that you can of course have a fully working Bootloader, but a dead Download Mode. This means you will not be able to flash a .KDZ/.TOT file the next time you are in big trouble! ^^
Okay to wrap up I should mention the EFS partition. The EFS partition stores your device's IMEI (and the serial number as far as I know) of your device. NEVER wipe it. With a empty EFS partition you can use your mobile as a brick, ok maybe you can use it as a media tablet, but that's it (WiFi still works, @Art Vanderlay tested; see below).
Again: if you got questions/additions/correction or see a mistake, post below, or PM me, I'll edit this post...
reserved
Great post. A thread like this should be the first thread you read as soon as you enter the LGG2 sub forum.
Expect a private message soon.
Also, reserved for possible future additions .
d00lz said:
Great post. A thread like this should be the first thread you read as soon as you enter the LGG2 sub forum.
Expect a private message soon.
Also, reserved for possible future additions .
Click to expand...
Click to collapse
And you could modify your signature now^^
Sunandroid said:
And you could modify your signature now^^
Click to expand...
Click to collapse
Nice write up Sunny. You can credit Dan Rosenburg for creating loki. I can also confirm that wifi still works without modemst1 and modemst2 aka efs. My phone suffers for this thread.
@Sunandroid
Perfect! This was all I was looking for. Now I finnaly understand how my G2 works and I'll most likely not need to ask more "noob questions" in this matter.
But I would like to ask some questions because I've left with doubts after reading the OP.
As long as I have /recovery/ and /aboot/ working, I can recover my device exclusively with software. Is this right?
I've concluded that you need /aboot/ to be able to enter in /recovery/ and with recovery you can mess up with any other partition.´
How can I tell if /modem/ found here is compatible with my device? Are all /modem/ partitions the same in the same models? For example, I'm from Portugal so I have a Portuguese D802 LG G2 (if I type its IMEI in a site, it recognizes it as portuguese). If I flash a German D802 modem or English or even American, considering that they are all from D802 would they work flawlessly with my device?
Why does /modem/ cause auto-rotation to work? What exactly is /modem/?
I have a backup of all the partitions in my laptop (made via TWRP). But what happens if I accidentaly lose my /efs/ partition? Can I flash another phone's /efs/?
Rayaxe said:
@Sunandroid
Perfect! This was all I was looking for. Now I finnaly understand how my G2 works and I'll most likely not need to ask more "noob questions" in this matter.
But I would like to ask some questions because I've left with doubts after reading the OP.
As long as I have /recovery/ and /aboot/ working, I can recover my device exclusively with software. Is this right?
I've concluded that you need /aboot/ to be able to enter in /recovery/ and with recovery you can mess up with any other partition.´
How can I tell if /modem/ found here is compatible with my device? Are all /modem/ partitions the same in the same models? For example, I'm from Portugal so I have a Portuguese D802 LG G2 (if I type its IMEI in a site, it recognizes it as portuguese). If I flash a German D802 modem or English or even American, considering that they are all from D802 would they work flawlessly with my device?
Why does /modem/ cause auto-rotation to work? What exactly is /modem/?
I have a backup of all the partitions in my laptop (made via TWRP). But what happens if I accidentaly lose my /efs/ partition? Can I flash another phone's /efs/?
Click to expand...
Click to collapse
Glad I could help you this way...
about /aboot and /recovery: yes you are right. It is even better, if you have an intact laf too. That's the download mode. But as long the other two work, you can fix the laf partition easily. But if you get into the situation, that only those two are working, better don't flash a bootloader (=/aboot). If it's the wrong one your device is bricked.
Aboot is the key to your device. Everything else is fixable. At least with a little bit of knowledge and time. But better don't try it out.
No, the modems are not all the same. There are (sometimes depending on the branding) extremely small differences between the basebands/modems. I personally never had the problem, that I couldn't get any connection at all. But that's not fatal. Just flash another one and try again if it works. Btw: I once made a test in some german forums with different KK basebands. I'm not sure anymore, but the differences were minimal and I think killed my connection totally.
If you loose your efs stuff, your device is a brick with extended functionalities. The IMEI and some other data stored in the efs partition is worldwide unique. So you can't just pick the one of another phone (except the other G2 is bricked or whatever). You need the IMEI for general network connection. So it will still boot up, but you won't be able to text or call anyone with this phone.
Okay ^^
So this is a full backup of all the needed partitions right? http://prntscr.com/76edu4
Should I convert these files to something like .img to be able to flash in the phone just in case I get something that disables my TWRP access?
Rayaxe said:
Okay ^^
So this is a full backup of all the needed partitions right? http://prntscr.com/76edu4
Should I convert these files to something like .img to be able to flash in the phone just in case I get something that disables my TWRP access?
Click to expand...
Click to collapse
Yeah, I guess so. As long as you ticked everything when you backed up (with blastagators TWRP!; the official one doesn't allow to backup the efs stuff), this should be fine.
Well you could. But tbh I have no idea how to convert those files into .img files. But it isn't necessary anyways: It's unlikely that you loose the efs data on your phone unless you brick it somehow. If the phone stays recoverable, The first thing you are going to do is: flashing bootloader, laf and boot.img. Then you will go back to stock through the download mode. Once you've done this it's an easy one to install twrp again and restore the efs backup. No one is gonna flash ~32 partitions by hand. There are "easier" and more usefull ways to recover the device.
Oh and btw: no backup contains the bootloader, laf and boot (recovery developer don't implement this for some reasons). But this doesn't matter. The only thing you really need is the efs backup (which partitions exactly you can see here). Everything else isn't unique and can be extracted out of kdz files and restored this way.
Edit: the two partitions mentioned here are
Sunandroid said:
Okay Download Mode time. It's part of the laf partition (laf.img). This partition is used by LG and it's PC software to recover the phone and bring it back to Stock. It's a partition in itself, but not completely independent of the Bootloader. It's because of this that you can of course have a fully working Bootloader, but a dead Download Mode. This means you will not be able to flash a .KDZ/.TOT file the next time you are in big trouble! ^^
Click to expand...
Click to collapse
My PC doesn't install any driver when my phone is on download mode,
On recovery mode (twrp) i have MTP access but on download mode i'm not having any access,
does that mean my download mode is dead?
GoPogoOreo! said:
My PC doesn't install any driver when my phone is on download mode,
On recovery mode (twrp) i have MTP access but on download mode i'm not having any access,
does that mean my download mode is dead?
Click to expand...
Click to collapse
This has nothing to do with this thread here. The issue is different. But I have no clue what it might be... If I can elaborate a maybe working answer I'm gonna answer you in the noob thread.
Sunandroid said:
This has nothing to do with this thread here. The issue is different. But I have no clue what it might be... If I can elaborate a maybe working answer I'm gonna answer you in the noob thread.
Click to expand...
Click to collapse
Oh btw i tried your (noob friendly) no download mode, no recovery mode ..... using slax,
when i typed ls /dev/sd* it's only showed my PC (only one sda) and there is no sdb, not even one
Weirdly i can access TWRP, but i can't make any custom rom boot,
Man this is frustating
I have a phone, G2 D802 Int., which probably has a corrupt EFS partition. I guess the owner broke it flashing incompatible things into it. As a result of the corruption, ESN/IMEI is lost. It shows null. But very interestingly, the EFS partition mustn't have been wiped because by chance of a boot among a hundred, it shows up the ESN. If by chance you come across to ESN, everything operates normally. And if you reboot the phone, ESN is gone again..
I managed to make recovery work again, by upgrading the phone to lollipop. (It was another time I came across ESN.) But no download mode, USB is never identified (unkonwn usb device), USB modes cannot be changed, unless by chance you come across, USB debugging is no more either.
I was thinking to backup some necessary partitions from a working phone of the same variant, but since it's "unknown device", I cannot query it as a disk. Neither it works in Ubuntu. ls /dev/sd* doesn't show the phone. It even doesn't show the working phone.
Any idea about how I can fix the corrupted EFS partition?
pisisler said:
I have a phone, G2 D802 Int., which probably has a corrupt EFS partition. I guess the owner broke it flashing incompatible things into it. As a result of the corruption, ESN/IMEI is lost. It shows null. But very interestingly, the EFS partition mustn't have been wiped because by chance of a boot among a hundred, it shows up the ESN. If by chance you come across to ESN, everything operates normally. And if you reboot the phone, ESN is gone again..
I managed to make recovery work again, by upgrading the phone to lollipop. (It was another time I came across ESN.) But no download mode, USB is never identified (unkonwn usb device), USB modes cannot be changed, unless by chance you come across, USB debugging is no more either.
I was thinking to backup some necessary partitions from a working phone of the same variant, but since it's "unknown device", I cannot query it as a disk. Neither it works in Ubuntu. ls /dev/sd* doesn't show the phone. It even doesn't show the working phone.
Any idea about how I can fix the corrupted EFS partition?
Click to expand...
Click to collapse
I luckily never had to try it, but scroll down a bit over here: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
I wish you luck!
Sunandroid said:
I luckily never had to try it, but scroll down a bit over here: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
I wish you luck!
Click to expand...
Click to collapse
Yes I know that, but since I cannot take the device to USB debugging mode, it's not the first step I could take. "USB device descriptor is failed", this is what I get when I plug the phone.
pisisler said:
Yes I know that, but since I cannot take the device to USB debugging mode, it's not the first step I could take. "USB device descriptor is failed", this is what I get when I plug the phone.
Click to expand...
Click to collapse
So what is the current state of your phone? You have twrp installed. Can you push stuff through adb when you are in the recovery (this is pretty important, since we maybe can fix the download mode this way)? Does it boot into android?
@Sunandroid, device operates normally except the voice call & data, since these depend on IMEI. The phone boots normally, and everything is working, only the IMEI shows as "null". Additionaly, cannot enter to download mode, no recovery installed, original recovery is working, which is used to do a factory reset only. No USB debugging, it says "USB device descriptor failed". Thus no adb.
pisisler said:
@Sunandroid, device operates normally except the voice call & data, since these depend on IMEI. The phone boots normally, and everything is working, only the IMEI shows as "null". Additionaly, cannot enter to download mode, no recovery installed, original recovery is working, which is used to do a factory reset only. No USB debugging, it says "USB device descriptor failed". Thus no adb.
Click to expand...
Click to collapse
From what I've read about this issue (device descriptor...) just now, it is not software but hardware related.
I've heard of people solving that issue but I couldn't manage to do. Gave the phone to my customer back after 4 days. Importer service put the phone out of warranty and offered him a motherboard replacement for 75 $ and it's pretty fair I think. After all it comes funny when he says he's gonna file a case about returning the phone and take his money back. Well, it's up to him to end up with nothing in hands after months of waiting for a case.
Shortly, this file has been closed without a reasonable solution.
Thanks for your effort @Sunandroid.
pisisler said:
I've heard of people solving that issue but I couldn't manage to do. Gave the phone to my customer back after 4 days. Importer service put the phone out of warranty and offered him a motherboard replacement for 75 $ and it's pretty fair I think. After all it comes funny when he says he's gonna file a case about returning the phone and take his money back. Well, it's up to him to end up with nothing in hands after months of waiting for a case.
Shortly, this file has been closed without a reasonable solution.
Thanks for your effort @Sunandroid.
Click to expand...
Click to collapse
Glad to hear that. Hitting the thanks button doesn't hurt.