yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] mexiking713:
No problem. Its like $40 shipped at the otterbox website so it seemed like a good deal.
[Samsung Infuse 4G] streetstyle54:
So I've been on this forum 24/7 for the passed 4 days since my phone bricked. Never tried putting any roms or anything on the phone, all stock. It just crashed on me. This is exactly whats happening:

I put the battery in, and as soon i do that, the samsung logo appears, then goes blank, only to reappear, and so on. I don't even have to press the power button it just automatically turns on. So eventually while searching the forums i followed laymans tutorial on how to make a jig, so i did. I thought i had it! But as soon as i saw download mode come up, it just went right back to a blank screen within 3 seconds, only to see that damn samsung logo. So I'm just curious, am I royally screwed?

Would love some input on this as i cannot find anything >.<
[Verizon Droid Incredible 2] Honoguma:
Please excuse anything I say that may seem laughable, ridiculous, or wrong, as I'm not very knowledgeable when it comes to these things.

I just recently found out that the Droid Incredible 2 is receiving an official Ice Cream Sandwhich update soon, but I'm rooted (used downgrade and revolutionary method), and have clockwork mod recovery flashed. I'm on Android 2.3.3. I want to return my phone to spotless, brick free stock in order to prepare for the ICS update.

Reading up on this, the closest I've come is finding a guide which involves flashing a stock hboot and downgrading to froyo and updating to gingerbread from there (can't post a link as a new user). I just want to know, will doing this remove everything, including CWM Recovery, and return it to stock? I fear that if even if I were to succeed at changing the hboot, I'd be stuck with CWM Recovery or super user or something.

If not, can I get instructions on how to return my phone to stock in preparation for ICS? I don't want to do this, try and update, and brick my phone because remnants of CWM or Revolutionary or Superuser remain on my phone.

Thanks to any reply in advance!
[Verizon Droid Incredible 2] knipp21:
why not wait till we get the ota and someone makes a rom put of it for us (like the same day) root is always better than stock.
[Verizon Droid Incredible 2] Honoguma:
I was considering that possibility also. An official rom could be flashed with cwm and would work just as well as an official ota update, yes?

Sorry, I'm very clueless when it comes to stuff like this.
[Verizon Droid Incredible 2] knipp21:
Example: someone wants stock 2.3.3....flash anybonesstock

When you want official ics...flash whatever someone prepared...probably condemned soul or nit
[Verizon Droid Incredible 2] Honoguma:
What exactly is condemned soul and nit?

I'm going to be honest though, the only reason I rooted in the first place was to freeze bloatware (not flash anything), I actually like HTC Sense and would feel much more at ease if I could just get rid of root and go back to the way my phone was right out the box.
[Verizon Droid Incredible 2] knipp21:
They are two devs that do mostly sense stuff...such as the sense 4 port being done.
[Verizon Droid Incredible 2] Honoguma:
Ah, thanks for the info. If I'm unable to find a way to get back to stock to do an ota (I prefer official, I have OCD over these things), I'll definitely check it out. Thanks!
[Verizon Droid Incredible 2] ChrisDDD:
Couple things, first, while the Inc2 will get ICS, it's anyone's guess when that'll happen, and I seriously doubt it'll be in anyone's idea of "soon". As it needs to clear Verizon, and there haven't been any leaks yet, I would be shocked if we got an OTA before fall. Second, an OTA will likely include a new hboot which would almost certainly address the exploit Revolutionary used to gain s-off. That could leave you with HTC's unlock as your only way to get root back, and HTC's unlock means you're forfeiting your warranty. Maybe you're ok with that, maybe not.

Honestly, if it were me, I'd download all the files and instructions from the RootzWiki restore to stock thread and put them somewhere for safe keeping. When the OTA comes out, you could restore then and receive it, or certainly by that time there will be roms available based on leaks of the OTA.

If you don't mind all the bloat, don't need root and are willing to potentially loose root permanently, then go ahead and restore to stock now, but I guarantee you'd be months premature if the sole purpose is the ICS OTA.

As for your concern about the restore leaving a trace of root or Clockwork... It won't. Your phone will be 100% stock - hboot, recovery, kernel and rom.
[Verizon Droid Incredible 2] knipp21:
Thanks. I didn't have the energy to type that all out :)
[Verizon Droid Incredible 2] ericmtnbkr:
One more thing. From what I've read/heard the Official Dinc II ICS will be Sense 3.6, where as the One V port that is being worked on is Sense 4.0.

I don't know what the differences are, but obviously 4.0 is 0.4 better than 3.6. ;)
[Verizon Droid Incredible 2] Honoguma:
Yeah, I don't want to go back to stock now, but rather wait until the update is close to release and restore to stock then. I'd rather not flash a custom from, as I'm kinda OCD about "official" and stuff. I don't mind losing rooting capabilities after the ics update.

As for the rootzwiki restore to stock thread, does it include directions specificially for the Inc 2, or is returning to stock a universal method for all devices? Don't I need specific files, tools, and direction for my phone and its firmware? Can you point me in the direction on where I can find these directions and files? I'm such a noob at this, and I apologize for not knowing anything. I just don't want to stumble across a thread where I download a wrong file and flash something bad and I'm screwed over for good.

Thanks SO much for all the help everyone!
[Verizon Droid Incredible 2] Honoguma:
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/

Is this the thread you were referring to, Chris? It seems sorta risky, but I'm willing to do it if I have a fighting chance. But AlpharevX, I'm assuming they mean Inc2's running 2.3.3 that were most likely rooted using the downgrade method with revolutionary? If so, I'd try it out.

Just a quick question, would there possibly be any roms that are identical to an official OTA update for the Inc2 when it comes out?

Apart from my obsessive desire to have an official firmware, I'm concerned about the camera. Excuse me if I'm wrong, but when I flashed cyanogenmod, the camera didn't seem as good as it was on stock htc sense. Not sure if I was just seeing things or not. :P
[Verizon Droid Incredible 2] knipp21:
Andybonesstock=our current stock rom...100%..someone will do he exact same thing when ics comes out...just trust me..
[Verizon Droid Incredible 2] ChrisDDD:
Yes, that's the thread, and it's specifically for the Inc2. AlpharevX and Revolutionary are the same things, so those instructions will work for both.

And yea, I agree about the camera. I recently flashed AndyBone Stock and the camera is definitely better. A shame because I really like stock CM7. I'm really hoping the CM9 based camera is better.
[Verizon Droid Incredible 2] Honoguma:
Thank you all for all the help! I'll try and do it once I sort out another problem of mine... :)
[Verizon Droid Incredible 2] joefrog1996:
Restoring to stock can be risky. Who wants to brick there device right before the ics ota? But that's just my opinion. Theres a video showing you how to unroot your device by Nat3mil. Type his name in youtube and go to his channel. The video is one of his first videos so it will be on the bottom. He also has a guide showing you how to root, I used it for my phone. Someone will have an ota rooted ics Rom the first day (FYI)

PS. While your rooted you should at least try different Roms. It can be very enjoyable. I know you will like it.
[Verizon Droid Incredible 2] Jcapone1119:
watch?v=tnlnWW8tsvo <<<< this will help
[Verizon Droid Incredible 2] dinc ii:
@ChrisDDD: the CM9 camera isn't very good imo. It doesn't seem to focus as well as stock, and when you zoom in on your pictures taken, they are grainy.
[Verizon Droid Charge] cnlson:
just wondering if anyone has managed to grab a copy of the new OTA so it can be rooted and odin'd

also wondering if the new rom is wacking the tethering apps (foxfi ect)
[Verizon Droid Charge] imnuts:
Awesome development going on here :rolleyes:

Honestly, people likely have it (like myself), but what is the point of posting it when what people really want are custom ROMs? I'm not posting a partial Odin package as it will just confuse people.
[Verizon Droid Charge] cnlson:
First of all, I really respect you, just downloaded the update for my wife's phone from your post on wiki since she is fully stock.

I am running EP4P, and I would bet there are probably plenty who still are also. all i want is an upgrade path that is quick, rather than having to increase my chances of something going wrong.

additionally, all i want is root, not debloat or deodex (i don't theme)

right now i have to flash to ep4d, then do the update, then reflash and all of the flashes are deodexed, and i'm concerned there won't be enough space deodexed.

sorry to have asked and again, Please accept my expression of respect for all you have done for the charge!
[Verizon Droid Charge] charlie_c:
There's already an upgrade path to get stock, bloated FP1 rooted that isn't that hard (3 steps basically). If you don't like any of the options here and you don't want to mess with going back to EP4D and going through the update and root process...I guess just wait and see if the combination you're looking for is released at some point. I think there's more interest by users and developers in applying the update to the current ROMs and themes.
[Thinkpad Tablet Android Development] khanning88:
This is a completely a stock Rom for the Lenovo Ideapad K1 Tablet. This is the latest update Honeycomb version 3.2.1, update 14_14_120109.

This will work for those lucky few who are plagued by the bootloader error when trying to apply the latest OTA.

Unsupported menu option selected: 1

Unrecoverable bootloader error (0x00000002)﻿

It does include all the original third party apps.

If you do not want the third party apps

Before flashing

1. Open the 'files' directory

2. Rename userdata.img to userdata.img.bak

3. Rename userdata_blank.img to userdata.img

This Rom is

NOT

rooted

Nvflash Windows Drivers

md5sum: 9aa3a4814ca63366329d85a22ed01f64

To boot into APX mode

1. Power off

2. Hold down the Vol - and the Vol +

3. While holding the Volume keys down, Power on

4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode. If using Windows make sure the drivers are installed

Instructions

Windows

1. Extract the K1_Stock_120109.zip contents to a directory

2. Double click the "flash-windows.bat" file

3. After the flash completes if you get any force closes you may have to do a factory reset. Settings > Privacy > Factory data reset

Linux

1. Extract the K1_Stock_120109.zip contents to a directory

2. Open a terminal and cd into the extracted directory

3. Copy and paste the following command

chmod a+x ./flash-linux.sh && chmod a+x ./files/nvflash

4. Run either

sudo ./flash-linux.sh

or from a root prompt

./flash-linux.sh

5. After the flash completes if you get any force closes you may have to do a factory reset. Settings > Privacy > Factory data reset

Download

K1_Stock_120109.zip

md5sum: 1ba3c55b4bfbd50495aeb22e66617629

Mirror - androidfileshare.com

Thanks to Whitesnake for being the Guinea Pig while we figured out what was causing the bootloader issue.
[Thinkpad Tablet Android Development] dms92969:
Umm.. Whitesnake.. not whitehawk LOL
[Thinkpad Tablet Android Development] Supaiku:
Looks like you put together a super package...

But I've got problems:

NVflash isn't working for me...

I just get an error:

C:\Adb\K1\NVFlash>nvflash -w
Nvflash started
rcm version 0X4
Command send failed (usb write failed)

My device is stuck in bootloops from flashing direct to K1_A301_13_13_111209_US.zip by renaming it update.zip and putting it in the Downloads folder.

Any idea what's going on? Should I just try to return it straight away?

EDIT: I'm bulled a bone head move. I was testing out nvflash, but in a directory without the files it needs! ha! All's well...
[Thinkpad Tablet Android Development] hmartinus:
Is this tools can applied to umts model?
[Thinkpad Tablet Android Development] blake2893:
Hey broo I really apreciatte your work but the links are down :( and I really need this because I got that Famous Bootloop.

Thanks :)
[Thinkpad Tablet Android Development] blake2893:
thanks for the mirror, but a little cuestion: the nvflash drivers are the same for all the tegra 2 devices?... cause the link of the nvflash driver is down...

thanks¡¡ :)
[Thinkpad Tablet Android Development] Jojo_Bizarre:
I want to use this w/o the 3rd party apps but there is no userdata_blank.img file to rename. Sorry if it's a noob question.
[Thinkpad Tablet Android Development] drx001:
Links dead

Please reupload.
[Thinkpad Tablet Android Development] jerryatherton:
Just get Kaschemme NVflash, his are current.
[Thinkpad Tablet Android Development] ana_mawjoud:
is there a similar solution for thinkpad ?

mine boots directly to "Booting Kernel Recovery Image" and hangs for a few second then powers down.
[Thinkpad Tablet Android Development] bimes:
hello,

plz update download links
[Captivate Q&A, Help & Troubleshooting] samwyze:
Hello fellow captivate users, I need some help here!

I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.

With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).

So far I've tried these oneclicks-

I897UCJF6 with bootloaders

I897UCKK4 with bootloaders

Plus various other packages that use odin to flash the different parts of the filesystem etc...

I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)

I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!

I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter :p)

Any help would be greatly appreciated

Cheers XDA Gurus :)
[Captivate Q&A, Help & Troubleshooting] captican:
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.
[Captivate Q&A, Help & Troubleshooting] TRusselo:
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.

odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..

do you need the jig? is the button combo not working? both volume + plug in usb to PC

if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.

but try this KK4 gingerbread heimdall package, with re-partitioning.

http://xdaforums.com/showthread.php?t=1386924

heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.

or...

try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.

give that a shot...
[Captivate Q&A, Help & Troubleshooting] samwyze:
Wow, quick replies guys, thanks.

I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.

I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.

Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.

Cool, so cable/ports are ok

but try this KK4 gingerbread heimdall package, with re-partitioning.
http://xdaforums.com/show....php?t=1386924

Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.

To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.

Thanks again :)
[Captivate Q&A, Help & Troubleshooting] samwyze:
I must be messing up - having trouble getting into recovery.

Here's what I did;

The links here: http://xdaforums.com/showthread.php?t=1386924 are dead, so I went straight to method 2.

Downloaded speedmod kernel from here: http://xdaforums.com/attachment.php?attachmentid=566807&d=1302623831

Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.

How long should I hold the 3 buttons down for? (How many bootloops?)

Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?

All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)

**edit

I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
For button combo to get into recovery--release when u see 1st att screen.

Or

Have u tried Adb (Android Debug Bridge) to get into recovery ??

Sent by XDA Premium App
[Captivate Q&A, Help & Troubleshooting] TRusselo:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
[Captivate Q&A, Help & Troubleshooting] samwyze:
Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.

Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
[Captivate Q&A, Help & Troubleshooting] studacris:
I've used adb during a loop plenty of times..on a couple devices.

My captivate, and my gf incredible.

Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business :)
[Captivate Q&A, Help & Troubleshooting] samwyze:
*removed double post
[Captivate Q&A, Help & Troubleshooting] samwyze:
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.
[Captivate Q&A, Help & Troubleshooting] b-eock:
You have to hit enter at the Right moment, it takes practice :P
[Captivate Q&A, Help & Troubleshooting] samwyze:
Lol, lucky I've got plenty of patience then!

Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?

Am I able to use adb from there to get an update.zip to internal sdcard?

How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!

Also am I right in assuming that because it gets to download mode it is eventually fixable?
[Captivate Q&A, Help & Troubleshooting] samwyze:
Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.

Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.

Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?

Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
[Captivate Q&A, Help & Troubleshooting] b-eock:
If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.
[Captivate Q&A, Help & Troubleshooting] samwyze:
Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.

There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.

I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course :p)
[Captivate Q&A, Help & Troubleshooting] studacris:
How about a non one click?

I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.
[Captivate Q&A, Help & Troubleshooting] samwyze:
Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
[Captivate Q&A, Help & Troubleshooting] samwyze:
Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.

I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.

Unless anyone has any other ideas I'm stumped for now.
[Captivate Q&A, Help & Troubleshooting] leezrd:
When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know

Edit: mabey designgears remembers what fix it when cognadian bacon porked it