Database Info

[Q] HELP - Just can't get into Recovery!

Hi everybody,
after endless nights and days of experimenting and crying I ask for your help.
My Aim: rooting my HTC One S C2.
So here is my story:
In my first attempt I unlocked my bootloader and tried to put a Custom Recovery on my phone. It failed. I got always stuck at the HTC screen with the red writing underneath the logo ("This build is for ...").
I then found out that I need the superboot.bat to root my phone.
So I proceeded to re-lock my phone and put a RUU on it to get back to the original Recovery.
All went well, so I unlocked my phone again via htcdev.com.
After that I tried to run the superboot.bat but again I am stuck at the HTC screen with the red writing!
I know that this screen should only appear for a few seconds and the phone should go into recovery but I am always stuck endless in this screen. To get out of it I have to soft reset my phone.
So I am not able to root it.
In a video I saw that on other phones the HTC screen with red writing has some kind of a "loading bar" on the upper right which appears after trying to access the recovery.
Well this bar doesn't even appear on my phone
Please help me I really don't know what to do further

same issue here, so subscribing to thread!

If you can get to download mode try to flash stock firmware with Odin. Search for a guide on youtube.
--------------------------------------------
Sent from my GT-S5830 running ImaGinary ICS.
Thank if it helped.It's there for a reason

Ähm isn't Odin for Samsung devices?
This is about HTC... Or does it work for both?

i recommend reading through this guide to rooting the one s. i've rooted quite a few phones using this method and it has worked flawlessly every time
http://forum.xda-developers.com/showthread.php?t=1583427

@HidaKureku - thats where i've got stuck; end of part two.
the recovery image seems to flash fine (both of them), and i've done the CWM recovery multiple times (some sites sugest that it works on the second attempt).
try to boot to recovery, and as per the OP it just sits there saying that it's for "This build is for HTC use only..." or whatever it says. no further. I've left it for 10mins in this state have have to power it off.
i have found that when i boot back to the UK retail ROM, it comes up with an error and wants to send it to HTC (i haven't yet been able to grab the error though).
has anyone sucessfully flashed recovery with the hboot 9.02.0001 image? i've seen a post on modaco with a user having the same problems as in this thread....

are you sure you're model has the S4 processor? if not, try this thread
http://forum.xda-developers.com/showthread.php?t=1785777&highlight=twrp

looks like i'm on the s3 version! twrp2 doesn't work either - same issue. (using openrecovery-twrp-2.2.2.0-ville.img)
seems the UK is one of these 'select' countries.
anyway - even an S3 compatible recovery isnt working....
I hope in not threadjacking here. @OP - if im intruding let me know and i'll create my own thread

No you are not intruding as I have exactley the same problem as you!
I'm glad that I'm not the only one I started to think I'm doing something completely wrong.
It's like the stock recovery is damaged even with the RUU version.
I just cannot get past this screen with the red warning!
My HTC One S is kind of new (about 3 weeks old). Maybe something changed with new models?

good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way

Yes!!!
That's it!!
Thank you so much
You made my day
Thread can be marked as solved!

now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly

HidaKureku said:
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
Click to expand...
Click to collapse
Thanks for the heads up, although that JB ROM in your sig says S4 in the title (thats about as far as i got )
@Schlengge - glad your sorted too i didnt even realise i was on s3 untill tonight; i thought all UK HOS's were s4's - seems not.

yeah XD i went back and looked at it and realized i got it confused with one rom i saw that was supposedly compatible with both processors (which struck me as odd) but there are a few roms out there for the s3, sadly not as many as for the s4, but you should be able to find one you're happy with. best of luck

veehexx said:
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Click to expand...
Click to collapse
well, thanks for that advice. It is kinda confusing to find a recovery for c2 version of the ONE S, cause any other recovery will not work with it. The twrp-team should definatly add the link to that on their website.

Lenovo IdeaTab A2107A-F

I am starting this thread to hopefully encourage discussion on the Lenovo A2107A-F tablet variant.
I am aware there is an existing thread on the A2107 here:
http://forum.xda-developers.com/showthread.php?t=1982334
but that thread is concentrating on the A-H (dual sim + wifi) variant which is somewhat different from the A-F (wifi only).
So far I have not found any custom rom development, which is disappointing as the stock rom leaves a lot to be desired IMHO. While the current OTA update is fine for web surfing, reading emails etc, HD video playback (particularly YouTube HD) is very poor. Also the recent OTA update forces an optimization of apps on bootup which leads to long boot times
You can root and install CWM by following steps 1-5 from the 1st post here:
http://forum.xda-developers.com/showthread.php?t=2044496
Note that "-Update 3-" mentioned in the post does not appear to work for the A-F model!
So, has anybody any leads on possible development on this tab?
Any tips on improving performance?

My first tip:
If after installing CWM you cannot get to the CWM recovery screen after powering down the device, look for for the file "/system/reboot-from-recovery.p". If it's there, either delete it or move it to some other place. This file restores the default recovery on a system reboot.
I got bitten by this a couple of times

Thanks for starting a separate thread for the A2107A-F. I'm new to Android devices and just got this one two weeks ago. I'd like to get rid of several of the apps that I have no use for and from what I understand that means I have to root it. I got lost in the details of the other thread, but I tried reading all of it. I'm on Vista and somewhere along the line I installed one of the suggested ADB drivers via PDAnet. Device Manager is showing Android Phone and under that Android ADB Interface. I wasn't sure if that matched closely enough with the step-by-step threads since I don't really think of the device as a phone, so I've been holding off on going further. I've tried using a few other drivers that were suggested in the large thread and some other threads, but Vista always tells me the current driver is the most up-to-date one.
Do you know if it's okay for it to say Android Phone rather than something else?
Thanks. I've got some other questions about the specifics of some of the other steps, but this is probably enough to get started.

My apologies in advance if my posts are too long and my questions are too basic for these forums. Feel free to point me somewhere else based on what I'm asking for. I'd honestly appreciate any leads towards my goal of getting rid of the bloat on this device and making it more responsive. (Wow! The portrait to landscape lag is really bugging me now after reading around here).
Anyway, my primary purpose is to remove the seemingly unneeded programs, services and widgets that come with the tablet. Maybe I'm just ignorant about these things, but at this time things like messaging (IMO), mapping, and some of the other default features are of no use to me. They seem to be eating up a lot of resources. I can kill some of the services I think they are associated with, but they keep popping back up.
I did watch the "noob" video (color me a tiny ant to be squashed) and did try to search for an answer to get me even started. I've read the huge main A2107A thread (80+ pages) and tried three of the suggested ADB drivers with my Vista 32 setup for my A2107A-F. The only one that even seemed to connect was ADPnet and it showed the tablet as a Android Phone. Maybe I'm just too paranoid, but after the multiple "brick" posts I'd like to make sure I'm on the right path before trying to "root" the device which appears to be the first step in removing all the extra stuff Lenovo added.
Not that it matters, but I've had the tablet for almost two weeks now and my favorite things are Slacker Radio, Scrabble, Roll It and Zen pinball. I do play Words with Friends with my wife, but I don't like it since some of the words they allow are not valid in Scrabble (which I used to play as an expert competitively face-to-face).
If you are so inclined, feel free to PM me for a Scrabble game. I promise I will not use anything other than my brain and the built in dictionary to make my plays. (I'm a bit rusty since I gave up competitive Scrabble in 2006).
So, long story short... Thanks in advance for any and all advice you can give on slimming down the Lenovo A2107A-F. And if you want an honest Scrabble challenge feel free to PM me.

As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root! You need to make that USB debugging is turned on on your device you have an entry in the device manager for ADB Interface (expand on the device which you have showing up).
I am no expert, and I struggled with this on my first go also
Once rooted you can then install Titanium Backup from the play store and use it to get rid of the bloatware! Proceed with caution however as it is possible to remove critical system apps!

degsie said:
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root!
Click to expand...
Click to collapse
Thanks! That's the type of test suggestion I was looking for to make sure I was on the right path with the driver.

So has anyone tried creating a rom for this tab yet? I've been doing some research into porting another rom to work on the A2107A-F, but want to make sure there isn't one already.

I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app

ssenemosewa said:
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
Click to expand...
Click to collapse
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!

Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?

ssenemosewa said:
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
Click to expand...
Click to collapse
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".

Kevin147 said:
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Click to expand...
Click to collapse
Although I have my A2107A rooted and tweaked to my satisfaction, there are a few lingering issues that I'd hoped an update would correct:
1) The neutered Bluetooth stack. The tablet is supposed to work with Bluetooth keyboards, mice, etc. It doesn't. Although I've gotten it to talk to an external GPS module, other Bluetooth data connections simply will not work. Oh, and Bluetooth audio? Forget about it!
2) Some settings that are present in stock ICS builds are just omitted in this one. As an example, the ability to specify a default TTS voice. It's present under settings in my wife's tablet and every other ICS build I've ever encountered. Not this one!
Sent from my IdeaTab A2107A-F using xda app-developers app

Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I was rooted too, lost root access (only with some apps!) after the 130221 update Feb 28. I'll try the same root procedure as before to see if I can get it back. Glad to see a thread on the popular US version A2107A-F. Maybe someone will port Jelly Bean to this tablet! Doesn't appear Lenovo wants to do it...
Rob

I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?

degsie said:
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
Click to expand...
Click to collapse
I'm in exactly the same boat as you. I'm getting the same exact error. except that I do not have CWM installed (I am rooted though). Perhaps there's a problem with the update.zip?
Something odd that I noticed however: After the tablet reboots into recovery mode, the update fails, and I go to browse for the update.zip, the sdcard/googleota directory is missing (along with everything that follows it alphabetically). They reappear upon normal boot. I've tried copying it to a directory closer to the beginning of the alphabet and it does show up while in recovery mode. But it still will not install.
Maybe I somehow do not have the available space to perform the update? Is that possible? I show plenty of available space on both sdcards. Could we somehow be below a certain ROM space threshold necessary for an update?

I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...

degsie said:
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
Click to expand...
Click to collapse
Well, I am running a stock rom. I am unwilling to "mess with success" until there's a 100% reproducible way of recovering if it fails. And, so far, everything I've read in the other A2107A thread has been hit or miss for the A2107A-F people.
Anyway, If the update is performing a verification test, then it my "virgin stock ROM" should certainly pass it. The only thing that I did is to root it. Hmmm...could the update be testing for that and refusing to install if it detects a rooted device? I would tend to doubt that, since the previous ota update went just fine. I lost root in the process but easily reapplied it afterward.
Thoughts?

Interestingly, I flashed the A2107A-F_S483_121115 rom (again, found in another thread) as I was having verification problems with the OTA update just released from lenovo which was available from the A2107A-F_S484_121211 flashed rom. While the S483_121115 rom appears to be older, I no longer get the option to update via OTA as the tablet is telling me that my s/w is up to date! Go figure.

It's really too bad this device hasn't taken off. If I actually knew how to dev then I would start developng ROMs for it. I'm enjoying it now that I have root and got rid of bloat.

Hey guys. Just wanted to say if someone can send me a stock rom and be willing to test, I'll try to do up a good rom for the -f models. I'd use mine for the stock rom, but I've edited a lot of the system, so no go there. If you have the stock rom or want to be a tester, let me know.

[Q] Indipad 10" Unblock or ROM

Hi, just recently some student tablets started to drop in my shop with problems, the latest one was an Indipad 10" made by LGS Caribbean, that is ALL the info I know about it since there are no labels anywhere in the tablet or the box, my guess is a generic Chinese re-branded tablet and it looks like is running ICS 4.0.1 but can't be sure since is locked with a number password. The client brought the tablet in cause her child was playing with it and activated the password screen lock and of course the child doesn't remember what he typed in. :silly:
I'm either looking to unlock the tablet, factory reset it or re-flash stock rom.
I already tried using the volume +/-/power combo for the recovery but it takes me to the android boot error screen, so I guess it has no recovery installed or it was deleted on purpose by the company. Also tried entering a lot of failed passcodes to see if it brings the account recovery option, but is a no go.
Did a Google search to see if I could also find a rom to flash on it but since I'm limited on the info about it nothing has come up.
Many thanks for any help.

No one?

Same thing right here. But i can tell you it is running android 4.0.4, and the build number is: crane_m1003h6-eng 4.0.4 IMM76D 20120921. Of course as you may know the 20120921 is the date so my guess is that it depends on how many updates those tablets have received already. Anyway, the recovery works, cus i have one in here working and you can access recovery from inside android(when you go to factory reset it gives you an option to do so, i did and it works perfect). But again just like you said, It wont work using hardware buttons. I was trying to find someone who can contact me from LGS Carribean but no luck at all. Just nothing, i have a working INDIPAD at this moment and thats how im telling you whats the firmware version and build. Like you said on your post, its an issue dealing with generic tablets it really is. I have not found even a similar enough firmware for the tablet to flash, but i can confirn you can use LiveSuitPack to flash them. Only issue is that i havent found a firmware to do so lol.... And ive look just about everywhere. Im going to run USB deview to check what the real hardware is and brand, if im able to find something ill let you know M8

Many thanks, client called in today and told her I'm still looking for a solution. Will wait for what you find.

Did you get this resolved?

Not yet, @home atm, so I'll check tomorrow for an update.

Seems we still on the black

Yes we are, so far i can tell you the processor is an A10, so its an A10 device. It shows as T10a for manufacturer, but so far thats all i can tell you. There might be a way to pull the firmware image from a working Indipad so that we have something to flash on the password protected ones. But for now, we are all waiting on something

Have same issue
enelyam said:
Yes we are, so far i can tell you the processor is an A10, so its an A10 device. It shows as T10a for manufacturer, but so far thats all i can tell you. There might be a way to pull the firmware image from a working Indipad so that we have something to flash on the password protected ones. But for now, we are all waiting on something
Click to expand...
Click to collapse
My mother-in-law is an English teacher and has several students with the same issue with a password they forgot or they locked the tablet on accident. I haven't been able to factory reset, but when you mentioned T10a, a quick Google search led me to show that EKEN makes T10a tablets.
I hope I'm not leading you down a rabbit trail, but here is their support site with manuals and firmware downloads
Also, searching on XDA apparently there is a way to get CWM on the EKEN T10a and instructions to flash to their latest ROM.
I haven't had a lot of experience with flashing ROMs, but I have flashed my personal devices before. So please let me know if this is possible in any way. I wouldn't want to mess something up. Well, I hope this helps.

mofongoloco said:
My mother-in-law is an English teacher and has several students with the same issue with a password they forgot or they locked the tablet on accident. I haven't been able to factory reset, but when you mentioned T10a, a quick Google search led me to show that EKEN makes T10a tablets.
I hope I'm not leading you down a rabbit trail, but here is their support site with manuals and firmware downloads
Also, searching on XDA apparently there is a way to get CWM on the EKEN T10a and instructions to flash to their latest ROM.
I haven't had a lot of experience with flashing ROMs, but I have flashed my personal devices before. So please let me know if this is possible in any way. I wouldn't want to mess something up. Well, I hope this helps.
Click to expand...
Click to collapse
Sweet, I'll do a hardware comparison tomorrow with EKEN T10a and see if they are identical devices (at least from the outside), if they match I'll just try that. The device is a brick atm so it doesn't matter trying to experiment with it.

mofongoloco said:
My mother-in-law is an English teacher and has several students with the same issue with a password they forgot or they locked the tablet on accident. I haven't been able to factory reset, but when you mentioned T10a, a quick Google search led me to show that EKEN makes T10a tablets.
I hope I'm not leading you down a rabbit trail, but here is their support site with manuals and firmware downloads
Also, searching on XDA apparently there is a way to get CWM on the EKEN T10a and instructions to flash to their latest ROM.
I haven't had a lot of experience with flashing ROMs, but I have flashed my personal devices before. So please let me know if this is possible in any way. I wouldn't want to mess something up. Well, I hope this helps.
Click to expand...
Click to collapse
OMG!!! IT WORKED!!!
Downloaded the T10A Firmware from the EKEN site, followed the steps and now the tablet is up and running perfectly!!! :victory:
Many thanks for your detective work

Omegadrive said:
OMG!!! IT WORKED!!!
Downloaded the T10A Firmware from the EKEN site, followed the steps and now the tablet is up and running perfectly!!! :victory:
Many thanks for your detective work
Click to expand...
Click to collapse
Awesome! I'm so glad I was able to help. I will go ahead and get mine done.

Its funny, but i have that firmware on my computer. Didnt even know why before this post. Now that i see your posts i realize i have flashed those tablet before using Eken firmwares lol.... Thanks a lot guys

What firmware worked for you? Im asking because i downloaded one of them and when i try to turn the tablet on it will keep booting up and wont flash the new firmware.

enelyam said:
What firmware worked for you? Im asking because i downloaded one of them and when i try to turn the tablet on it will keep booting up and wont flash the new firmware.
Click to expand...
Click to collapse
The one for T10A, version "T10 G-SENSOR6225".
I also had a bit of a problem at first trying to boot it into flash mode, but what I did was go to the device manager in Windows and saw that there where 2 copies of the special driver that the "LiveSuitPack_version_1.09_20111101.exe" installs, one with the checkmark like they said, the other I assumed was the tablet connected, so I deleted the one with checkmark and tried again, this time it went through and started the flashing process which took less than 2 minutes.
Straight after attaching the cable, and whilst still holding down the volume+ button, start pressing the tablet power button repeatedly. This (slightly frenzied) procedure puts the tablet into update mode.
Click to expand...
Click to collapse
That was the tricky part, to make it boot into flash mode, it has to be fast between connecting and starting to press the buttons, I took like a 1 second delay between the two things.
Also, got to point out I didn't do the CWM or the root mod, just did the firmware flash cause that's what the client wanted.

Its allright buddy, and thanks. Thing is that i was trying to update it as it said on the Ekken website. But the tablet didnt accept the SdCard update at all. I told you it should be done using LiveSuit and yet i was afraid of bricking the device using LiveSuit ha ha.... Thanks a lot guys, case solved. It took all of us to do so but hey, we made it!!!!

Hi, i have same indiPAD only camera front, i tried flash another rom EkenT10-6225-20120815.rar but touch not work good, works inverted and camera not work.
Im trying download firmware from server eken but very slow, can you shared anoter server please?
thanks

Pulian said:
Hi, i have same indiPAD only camera front, i tried flash another rom EkenT10-6225-20120815.rar but touch not work good, works inverted and camera not work.
Im trying download firmware from server eken but very slow, can you shared anoter server please?
thanks
Click to expand...
Click to collapse
Their server is kinda slow but I use Free Download Manager to download big files and speed up the download.
Also remember this was an experiment and it worked by chance, so no guarantee that it will for every indiPad out there, specially if the manufacturer changes the hardware, you should check the hardware info on the tablet just to make sure we are talking about the same tablet model or you could brick your device.

thanks bro, i know about rom experimental, i think same tablet from Puerto Rico, indiPAD, same eken t10a.
Can you tell me please what file worked on your tablet? i see some files
sun4i_crane_m1003h6-t10a-mc32x0-20121012.rar 274256 KB
t10.rar 200563 KB
t10_2axis_6225.rar 208067 KB
t10_3axis_7660.rar 208078 KB
t10a-mc32x0-20121012.rar 274256 KB
And maybe possible did backup rom from working tablet too. If you can and have one piece we can dump rom.

Pulian said:
thanks bro, i know about rom experimental, i think same tablet from Puerto Rico, indiPAD, same eken t10a.
Can you tell me please what file worked on your tablet? i see some files
sun4i_crane_m1003h6-t10a-mc32x0-20121012.rar 274256 KB
t10.rar 200563 KB
t10_2axis_6225.rar 208067 KB
t10_3axis_7660.rar 208078 KB
t10a-mc32x0-20121012.rar 274256 KB
And maybe possible did backup rom from working tablet too. If you can and have one piece we can dump rom.
Click to expand...
Click to collapse
t10_2axis_6225.rar is the one I used.
The only working tablet I had was the one flashed, the client already picked it up yesterday, so sorry.

Trying to Serial #

I'm trying to find the sbk#on my tablet I've bought this from a person on eBay it works awesome... It already came with root but with any device I get I full flash to stock to clean up any old crap the other person. May left.... The tool I'm trying to use asking if I know the sbk# but its not in the tablet nor in the about section....
I've googled every possible forum I could find and have put a couple of custom ROMs but can't find serial # anyway to retrieve without original documentation
AOKP 4.2.2 by Task650
Ktoonz Kernel w/KingBeatz
TF101 A.R.H.D ICS w/KingBeatz

crashpsycho said:
I'm trying to find the sbk#on my tablet I've bought this from a person on eBay it works awesome... It already came with root but with any device I get I full flash to stock to clean up any old crap the other person. May left.... The tool I'm trying to use asking if I know the sbk# but its not in the tablet nor in the about section....
I've googled every possible forum I could find and have put a couple of custom ROMs but can't find serial # anyway to retrieve without original documentation
AOKP 4.2.2 by Task650
Ktoonz Kernel w/KingBeatz
TF101 A.R.H.D ICS w/KingBeatz
Click to expand...
Click to collapse
If you look at the bottom of your tablet the beginning of the serial will start with a B## or some start with C##. If you tablet serial starts with a number that is lower than B70, it's SBK#1. If it is greater than B70 (or C) it's SBK#2. If it's B70 it's iffy because they changed it halfway through those. There is also a tool here (http://forum.xda-developers.com/showthread.php?t=1232612) that can detect your SBK#. Hope this helps.

That tool only works on mac.
What you can do is just run both versions of NvFlash, and the one that works is your Sbk.
The Sbkv2 started with the B70K series. Below that is Sbkv1.
Using the wrong Sbk will only return a 'wrong sbk' error, nothing damaging.
You also don't need to full flash to stock, just use TWRP to run the ARHD Superwipe full script, then wipe everything except external SD in the wipe menu, good as new. NvFlash is also total wipe if you really want too though.

Revive Soft Bricked Device through Identical 2nd? (LG l21g Destiny Tracfone)

Long story short:
How do i get my current working android device to revive an identical soft-bricked device. More challenging than you think: there is no boot menu accessible in the devices. Which means the only other choice is to use a usb connection to a PC to perform all tasks, i.e. create a rom system image backup of the working device, then use that to restore the system onto the soft-bricked one.
So is there a way to revive the s/bricked device with a rom image of the working twin?
The long story:
After using the super-sume app, my device got softbricked. Phones of my type are uncommon and are therefore not worked on by the android hacker community as much as flagship devices are. And little is known or discovered about them. So after doing more research, i've sadly come to know that there are other users here and there, having suffered the same problem as I. But enough about that.
As far as i've read and come to understand, i would need to re-flash the firmware to bring it back from it's softbrick issue easiest/safest way.
Though am not sure how the android platform would work. With PCs, i could restore a messed up system from a cloned image. What i need to confirm is if the firmware is separate from the OS (roms i believe) the same way device drivers are separate from the windows OS on PCs.
So am not sure if flashing firmware is enough and would need to stock rom too. Or is the rom considered both firmware and OS all in one?
I mentioned "restore from a clone image backup" because I have another, exact same model of my softbricked device, that functions still properly.
So i wonder if there is a way that i could use my working device to revive the soft-bricked one. In the sense that i would need to make a system image copy of my working one, to restore onto the s/bricked one.
What the problem looks like when starting the phone:
As for the softbrick appearance, the phone boots into the LG logo screen and is frozen there. It doesn't quite look like it's boot looping since the screen Never fades to black quickly just to come right back. It's just frozen there. This recovery mode screen is the only other thing i can get to besides the frozen LG screen: https://wcrates.files.wordpress.com/2015/03/lg-g3-recover-mode.jpg
I've come to learn (but may need correction on) that Tracfone devices are deliberately handicapped in a way i've never seen before. That is, their devices have no other boot type of menu besides the Recovery Menu (found before os begins boot) that is basically a factory reset. It just deletes all user data and resets system settings so that the phone works like it would at first when right out of the box. For the s/bricked device, that screen can be accessed, though executing that just resorts to the frozen boot screen again. If there is a boot menu to backup/restore from, clear cache, install from zip and what not, then please enlighten me. Because as i've tried everything, the tracfone-devices have nothing compared to non-tracfone-devices
So in order to install an updated rom, i may need to get into a type of system boot menu from where i would be able to select the option to install a rom or update it and what not. To some degree i assume that connecting the device through USB to a computer, one may do the same rom installation action through the PC, but it's in cases like these where i would need the help of and expert's first hand experience with such things or ways.
I don't mind if you want to leave a link to some tutorial some other guy has made that may closely related to (if not exactly) to help solve this issue. But i do prefer to get into contact with someone who i can report to with how the solution process is progressing. Mostly because me being a noob at this point of my android experience, but am confident since i've done this with pc's a lot.
I'm still trying to figure out what most of the android community speaks of when it comes to methods of backing up their stock roms and what kinds of software on PC or apps on the device are needed to accomplish a worthy backup. I do realize i'd need ADB and what other LG device compatible PC software out there. Here is a link where i think firmware files can be found, but since it's all in Chinese, i'm not sure how reliable the site is/can be. It's been about a month since i contacted some of their users. At this point it seems like they're no hope:
http://mobile.gaodi.net/Firmware-669539-1-1.html
I hope that i can find success so that i can post it up to help others who are in the same situation as me, and also for the many more who may yet fall into this situation.
Any help will be greatly appreciated.
Thanks.
Device: LG l21g (aka lgl21g) Destiny (model) by TracFone
Android: 5.0.1