Related
As a Galaxy S i9000 owner I am curious, has anyone yet got any idea how updates and general ROM flashing are to be done on the Nexus S? I understand OTA will be likely for the PDA code but how about the baseband? Do Google take care of the modem or do Samsung?
And since we use Odin to re-partition and re-flash the ROM in the SGS I wonder how this is performed on the Nexus line?
I am very happy to see Kies left behind but I also see no software for the Nexus S at all. Even my Motorola Milestone had some sort of desktop connectivity for when things went wonky..
Is there any reason we would not use rom manager to flash new roms since that is how we have been flashing our cw recovery? Seems that would be the easiest solution just like on the n1
generalagony said:
Is there any reason we would not use rom manager to flash new roms since that is how we have been flashing our cw recovery? Seems that would be the easiest solution just like on the n1
Click to expand...
Click to collapse
My Android life has been Milestone > SGS, so I am not familiar with that one, we use Odin over USB on the Galaxy line.
Ok, that is interesting to know. Does that also include the modem code though?
If by modem code you are referring to the radio image; yes. Most all files can be flashed via clockwork recovery. It it all i ever used on n1 to flash roms, kernels, and radio files.
generalagony said:
If by modem code you are referring to the radio image; yes. Most all files can be flashed via clockwork recovery. It it all i ever used on n1 to flash roms, kernels, and radio files.
Click to expand...
Click to collapse
Superb, I will have to have a look into CWR then. Had little cause to so far.
If you are rooted already the easiest thing to do I download rom manager from the market and flash cwr through there. It has been updated to the newest version through rom manager and is completely painless
Fastboot should also work depending on how the file you want to flash is released.
fastboot recovery new_recovery.img
fastboot system custom_rom.img
fastboot modem new_modem.img
etc, etc, etc...
Think of fastboot as sort of Google's version of Heimdall (3rd party Odin replacement)
Thanks all for the input, I need to get the phone next. UK delays and such.
Samsung really went somewhere annoying by forcing a USB update system. Nexus S sounds like a happier time.
nailerr said:
Thanks all for the input, I need to get the phone next. UK delays and such.
Samsung really went somewhere annoying by forcing a USB update system. Nexus S sounds like a happier time.
Click to expand...
Click to collapse
This seems like a world of difference from HTC RUU's
JD
when i held volume down + power i was prompted with enabling the ability to install a custom OS...
does this effectively unlock the bootloader?
onicrom said:
when i held volume down + power i was prompted with enabling the ability to install a custom OS...
does this effectively unlock the bootloader?
Click to expand...
Click to collapse
That's called "Odin" mode or "Download" mode. No, at the moment and (probably not in the future either) it will not unlock bootloader.
This device is quite different from previous Samsung tablets, as I can't find the key combination nor the adb command to boot it in bootloader mode.
Any devs can shed some light on this issue?
im trying to figure out how to use this odin business ive only ever had fastboot enabled devices!
i used osx and when i boot into odin mode and spin up heimdall its not detecting my device should it?
onicrom said:
im trying to figure out how to use this odin business ive only ever had fastboot enabled devices!
i used osx and when i boot into odin mode and spin up heimdall its not detecting my device should it?
Click to expand...
Click to collapse
You have the proper drivers installed?
onicrom said:
im trying to figure out how to use this odin business ive only ever had fastboot enabled devices!
i used osx and when i boot into odin mode and spin up heimdall its not detecting my device should it?
Click to expand...
Click to collapse
Heimdall should find the device if you the latest drivers installed.
You can root the device from recovery and yes the boot loader here is "unlocked " .
Sent from my GT-P6800 using xda premium
Samsung devices do not have "fastboot" mode.
They have "download" mode. Which you can flash firmwares, kernels, modems and such with Odin and heimdall.
Also Every since the SGS2 the "bootloaders" have not been locked.
thanks to the both of you.
ive installed heimdall 1.3.1 tried both the gui and cli mode no luck finding my device. i dont have a windows machine so no odin for me
is there anything that needs to be done inside honeycomb to unlock something?
onicrom said:
thanks to the both of you.
ive installed heimdall 1.3.1 tried both the gui and cli mode no luck finding my device. i dont have a windows machine so no odin for me
is there anything that needs to be done inside honeycomb to unlock something?
Click to expand...
Click to collapse
Why no Odin for you? I have Odin on my Win 7 64x machine and Odin works fine. Make sure you are using odin 1.85. To my knowledge was the latest release.
Here is it attached so you do not have to search for it. Just unzip and use it Make sure you have drivers installed of course.
thanks for the link but no odin for me because i dont have a windows machine. only osx
Odin/Heimdal download mode is the be all-end all preventer for borkage for Samsung phones/devices. (I've had a Captivate & Infuse)
Heimdal should only show recognition when trying to flash something. Hmm. May need to look into other things if it doesn't work. :/
onicrom said:
thanks for the link but no odin for me because i dont have a windows machine. only osx
Click to expand...
Click to collapse
www.virtualbox.org
antiochasylum said:
Why no Odin for you? ...
Here is it attached ...
Click to expand...
Click to collapse
I have a feeling this attachment is no longer reachable now that Megaupload has been disabled. Do we have alternate places to host attachments now?
antiochasylum said:
Samsung devices do not have "fastboot" mode.
They have "download" mode. Which you can flash firmwares, kernels, modems and such with Odin and heimdall.
Also Every since the SGS2 the "bootloaders" have not been locked.
Click to expand...
Click to collapse
I believe only some of the original 7" Tabs had truly locked bootloaders.
The closest newer devices have is the "custom binary counter" - It trips a flag/warning if you flash something unsigned, but does not prevent it from executing.
Note that some newer Samsung devices changed the download mode protocol and broke Heimdall, although it seems to more typically be "non-Hummingbird/Exynos devices" that have issues. Heimdall won't talk to anything Tegra or Snapdragon based, but will talk to the new Tab 7 Plus. Don't know about the 7.7.
Note that some newer devices are "middle" cases where Heimdall will sort-of work but won't actually flash anything - the Galaxy Player 5.0 (and maybe 4.0 too?) are examples of this.
i havent been able to get heimdall to recognize the device... but i may be doing something silly as ive never used odin before.
I have flashed my 7.7 with odin 1.85 already and it has worked... just a heads up..
Sent from another Galaxy...
Tab 7.7
onicrom said:
i havent been able to get heimdall to recognize the device... but i may be doing something silly as ive never used odin before.
Click to expand...
Click to collapse
You have to be in download mode - if it still doesn't recognize the device in cases where Odin works, I guess that the 7.7 uses one of the newer protocols.
Entropy512 said:
I believe only some of the original 7" Tabs had truly locked bootloaders.
Click to expand...
Click to collapse
Actually this is not correct. The original 7" Tab was never in the wild with locked bootloaders. Only some leaked test firmwares had locked bootloaders - that is what all the fuss was about back then, because once you had them installed, flashing a newer or older official firmware did not remove the lock. There has never been a P1000 firmware on device in-store or an official KIES upgrade with locked bootloaders. All official firmwares have completely unlocked bootloaders.
The 8.9" and 10.1" Tab family do have unlockable bootloaders, most of them unlockable with fastboot, but on the 10.1v specifically that is only possible with some bootloader versions. There is firmware update to unlockable bootloaders, but still the device comes locked by default.
Interestingly, the Samsung-built Nexus family has an unlockable bootloader, but any use of Odin automatically unlocks the bootloader (same as fastboot oem unlock would). This is something the 8.9" and 10.1" Tab family does not do, you need to unlock first (if I'm not mistaken).
The 7.7" is based on the SGS2/SGNote family of device, which is a completely different heritage from the 8.9 and 10.1 family. The other Exynos based devices are completely unlocked out of the box - I assume the same is true for the 7.7 ?
(Note the subtle differences in this comment between: (a) locked bootloader (b) unlockable bootloader and (c) unlocked bootloader)
OK, I had my history wrong on the original Tabs.
I haven't seen any way to unlock the 10.1 once you got SBK-locked - but the SBK lock only affects flashing with nvflash. So maybe that would be a "locked flasher?" I have never seen the 10.1 perform any enforcement of code signing when booting stuff that has already been flashed.
Entropy512 said:
OK, I had my history wrong on the original Tabs.
I haven't seen any way to unlock the 10.1 once you got SBK-locked - but the SBK lock only affects flashing with nvflash. So maybe that would be a "locked flasher?" I have never seen the 10.1 perform any enforcement of code signing when booting stuff that has already been flashed.
Click to expand...
Click to collapse
Exactly that is what has happened to my 10.1v, it seems, just yesterday as luck would have it.
(Might be only the v variant does that, though)
Chainfire said:
Exactly that is what has happened to my 10.1v, it seems, just yesterday as luck would have it.
(Might be only the v variant does that, though)
Click to expand...
Click to collapse
Maybe - as I understand it the v is quite different from the stock 10.1.
The 10.1 non-v has its own set of annoying variants though - Wifi, 3G, Verizon LTE, and one other one. Plus the Google I/O versions had some slight differences from the Wifi (I think they have a slightly different .pit, which is why fastboot can't easily be flashed on non-I/O wifi units.)
For the non-v - You can get SBK-locked if you're not careful. What's annoying is that SBK-locking actually makes Samsung MORE likely to have to offer warranty service - if a device isn't SBK-locked, it's completely unbrickable, as nvflash capability is built into the CPU itself (Just like GalaxyS phones with Unbrickable Mod, and the 5 inch Galaxy Player/Galaxy S Wifi units). If it's SBK-locked - well, if you corrupt the bootloaders and disable Odin mode you're toast, since nvflash won't work. Somewhere around 50% of the initial 10.1 wifi units shipped without SBK locks, but all of them shipped locked eventually and then if you weren't careful, various OTA updates would burn the eFuses for SBK locking if they weren't already burned.
I just rooted my Acer iconia tab a500. I am on the official ics 4.0.3. Can anyone provide step by step guide how to install custom rom for this tablet? Also which custom rom that you recommended? I thanks
Sent from my SGH-T989 using xda premium
Please, me too. I just bought mine too and is rooted, but my cell phones were much easier than the tablets. Either that or I just don't have the patients anymore. Maybe a dummies way to install custom rooms on a500? Lol.
Sent from my A500 using xda app-developers app
fe1ixs said:
I just rooted my Acer iconia tab a500. I am on the official ics 4.0.3. Can anyone provide step by step guide how to install custom rom for this tablet? Also which custom rom that you recommended? I thanks
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
slayinu said:
Please, me too. I just bought mine too and is rooted, but my cell phones were much easier than the tablets. Either that or I just don't have the patients anymore. Maybe a dummies way to install custom rooms on a500? Lol.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Hi guys welcome to the weird and wonderful world of the acer tab!!!!
Things are very different with this device, whats 'normal' for other android devices is not 'normal' for our tab!!!!
So first of all, dont try installing cwm or a rom the 'normal-this-is-the-way-I-did--it-on-myphone', you will end up with a brick!!!
2nd, you both have working systems at present, so we'll try to keep it that way.
Open up a file explorer and navigate to this:
/sys/firmware/fuse/acer_cpuid
One of the first things that are different is this: acer_cpuid
It should look something like this:
288424344009597 - now u need to add a 'zero' to the front:
0288424344009597 - this is your cpuid, back it up in multiple places if need be, just dont ever lose it - IF anything 'goes wrong' at any time you will NEED this number to save your tab from eternal brickdom!!
3rd once you do get your 'cpuid' go to the 'sbk generator' here.
This generates your 'sbk' or secure boot key and will give you something like this:
0x93588800 0x33CE8901 0x0BED6D03 0x30737899.....
OK then, now you have your cpuid/sbk you can start thinkning about what rom you want to install on your tab.......
Read the OP(Original Post) of your desired rom. This will tell you EVERYTHING you need in order to flash it - remembering always that 'Acer' does not do things the 'normal' way!!!!!!
Most of the custom ICS/JB roms on here all require the 'patched / unlocked bootloader'... In fact, even installing a custom recovery, cwm, twrp or public recovery, for the first time....will require the BL to be 'patched' first....and yes, even flashing this is not done the 'normal' way....tho the process can be complicated there are PLENTY of guides and auto tools to make it easier for you....
The 'patched bootloader flash' will also include a 'custom recovery' too, and you can choose from 3-4 options....amazing but i'd advise to use cwm 1.7.3, until u get up and running, after that you can go crazy flashing anything you like!!
So basically there are 5 main steps to getting a custom rom installed.
1. Install the Acer Drivers and the android_sdk drivers
2. Get your cpuid and generate your 'sbk'
3. Your desired rom is on your external sd card
4. Put your tab in 'apx mode' which allows u access to download mode
5. Install the patched v8 bootloader/recovery - either manually using nvFlash or using the auto tools.
Personally I prefer the manual nvFlash method, if you get an error it will at least give you an error message...the auto tools will just get 'stuck'
Check the 'bootloader' thread OP for a guide to manual nvFlash and the patched bootloader package here
There is also a step-by-step in my sig!!!
If you want to use the auto tools then apxFlash tool, or afterOTA tool you can find both in the 'bootloader' thread. And a step by step for apxflash tool also in my sig....or this excellent one here by user jdgM3NT4L here...
please be sure to read these posts very carefully and if there is something you do not understand then please dont hesitate to ask , there are plenty on here who will help you thru the process....AND its easier to offer help at this point rather than trying to do so when you've bricked it.....
As far as roms are concerned, you cant go past 'civato's FLEX roms' very stable and no issues i'm on cm10 and havent had a problem with it.....Of course it depends on what you require but I'd start with one of the flex ones.
Most peeps here have no trouble with this process, those that do, usually try things the 'normal' way, then find out they need their cpuid/sbk to get out of trouble and of course they dont have it....this makes things most difficult.... there are a few tabs with motherboard issues that have needed to be sent to acer....other than that, he only other issue you may have are driver related, check out the cpuid thread for anything driver related and lots of other background info too....theres also a zip file there that has a mini-sdk kit, to save u downloading the full android-sdk....
i think thats all i can think of at the moment, sorry for the long post and all the caps and bold text - just trying to save you alot of unnecessary grief...
Good luck with it all and remember....in this forum things are not 'normal' :laugh::laugh:
Wow, a lot of stuff to do just to flash a from huh. Lol
Sent from my A500 using xda app-developers app
Lol, as always preparation determines the success of the final outcome....and yeah with the tab 95% of yr time and energy is spent preparing!!! The actual flashing process takes only a few minutes...
Of course u could revert to hc 3.1 where everything is 'normal' i.e. one click root, flash cwm, flash rom, done....
Gosh, even hc 3.2 was locked down and unrootable....
So in the grand scheme for us to even be able to have stable ICS roms, let alone cm10 on the a50x.is.purely down to those wonderfully clever devs we have here..who were never gonna let a.locked bl, get in their way..
OK its complex I'll admit, but stock ICS is c**p and the lives of our tabs extended past wot Acer ever thought....and guys like gersma and.blackthund3r have built auto tools to make things easier
Anyways, its.well worth the
effort and is actually alot simpler to do than it is to describe how to do it...think of.trying to explain how to ride a bike and writing all those steps out....much easier to help them thru it by just getting them on the darn thing and doing it....dontcha think??
Sent from my GT-I9300 using Tapatalk 2
Yeah, I hear ya loud and clear. I wouldn't mind goin back to stock 3.1 , I kinda liked the hc. Ohwell
Sent from my A500 using xda app-developers app
---------- Post added at 07:27 PM ---------- Previous post was at 07:21 PM ----------
But as soon as I get home on my PC I'll start trying out this method. Hopefully I don't end up with a paper weight. Lol. Thank you very much for your response on this subject.
Sent from my A500 using xda app-developers app
Well, I could give u a a d/l link for 3.1 if u really do wanna go back....but I think gersma's afterOTA tool can do it too, tho I've Neva used it for that so can't really comment....
Oh, one other thing, you'll wanna back up all yr personal stuff, music, photo's and wot not especially going from one build to another, and most of the custom ROMs require a complete wipe and format of yr data partition too before install, just so u know!!
Sent from my A500 using Tapatalk 2
Yeah ,I'll take the link, I liked it better than 4.0.3 is it an original , or a rooted
Sent from my A500 using xda app-developers app
slayinu said:
Yeah ,I'll take the link, I liked it better than 4.0.3 is it an original , or a rooted
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
its factory stock but easy to root and get cwm installed, will have to w8 till i get home 2nyt to upload....
oh there myt be one in blackthund3rs stock rom thread in dev forum...i think
Sent from my GT-I9300 using Tapatalk 2
wow dibb, thank you so much for a helpful response!! Really enlightened me about how far off I was about the update process (compared to updating phones) and yet close enough to what I had to go thru for the Viewsonic GTab.
I'm currently on stock 4.0.3 rooted for A500. I have obtained my cpuid and SBK. When I go to recovery mode, I see a droid with triangle and exclamation mark. I tried flashing twrp but I still saw the same droid. I now know that I need to flash a different bootloader with recovery included.
My question is that if I flash the new bootloader which will allow me to put a custom recovery, during that process will my current ROM be removed or wiped out? If so, what do you recommend for backing up the app in the current stock ROM? Titanium Backup? BTW, I don't have an external SD card; all I'm using is the internal 8GB
Thank you for your help!!
def need external SD , it will help out alot
Sent from my A500 using xda app-developers app
artbybart said:
wow data, thank you so much for a helpful response!! Really enlightened me about how far off I was about the update process (compared to updating phones) and yet close enough to what I had to go thru for the Viewsonic GTab.
I'm currently on stock 4.0.3 rooted for A500. I have obtained my cpuid and SBK. When I go to recovery mode, I see a droid with triangle and exclamation mark. I tried flashing twrp but I still saw the same droid. I now know that I need to flash a different bootloader with recovery included.
My question is that if I flash the new bootloader which will allow me to put a custom recovery, during that process will my current ROM be removed or wiped out? If so, what do you recommend for backing up the app in the current stock ROM? Titanium Backup? BTW, I don't have an external SD card; all I'm using is the internal 8GB
Thank you for your help!!
Click to expand...
Click to collapse
Yes u need the v8 bootloader to get a recovery installed...
Always check the original post of the rom you install for special instructions regarding bootloaders.....this applies to all custom Roms even stock pre rooted ones.
Yup TB to back up yr apps and data - dont restore immediately...make sure everything is stable first.
If u dont have an ext. SD card, the EUU method doesn't require one, and as slayinu said, it would make it easier if u had one especially for the update.zip methid
Im sorry...
I have the a500 running ota 4.0.3....well from the official app. I have it rooted and running superuser yet I downloaded the Acer recovery installer app from the market and get the recovery verified failed message when booting into any custom recovery and the dead android with the exclamation mark....I know I need a patched or an unlocked boot loader but I cannot find one I downloaded the afterota but it doesn't do anything on my computer...idk what to do the frustration is gonna make me break this thing and just go buy a newer tab running jb ....help please!
famousnerd1 said:
I have the a500 running ota 4.0.3....well from the official app. I have it rooted and running superuser yet I downloaded the Acer recovery installer app from the market and get the recovery verified failed message when booting into any custom recovery and the dead android with the exclamation mark....I know I need a patched or an unlocked boot loader but I cannot find one I downloaded the afterota but it doesn't do anything on my computer...idk what to do the frustration is gonna make me break this thing and just go buy a newer tab running job....help please!
Click to expand...
Click to collapse
Seems weird afterota "doesn't do anything"...did you install the drivers?? Did it give u yr cpuid/sbk you cannot do anything without this AND if u muck things up its the only thing that will get u unbricked? Are u using a micro USB cable? Do u have USB debug enabled?
If u go to the root guide in my sig you'll find d.load links and all the guides to help u install the v8....take special note of the boot.p file u need to rename or delete in /system....
For more info on getting yr cpuid/sbk see the cpuid guide in my SIG or the sticky in dev forum...
Sent from my GT-I9300 using Tapatalk 2
obviously..
I'm too dumb to figure this out...idk how to get my cpuid none of the ways in your "where's my cpuid"guide worked.I don't want to stay stuck on ota 4.0.3 but apparently I have to..thanks for your time and your advice,unfortunately I wasn't able to use it properly.
Well, it seems it's not just you being dumb ...
I tried the same - original OTA 4.0.3 and rooted my A500. Now tried to use the 'AfterOTA'-Tools, but getting stuck in step 3 of 4 (maybe i just need to insert a SD-Card in the Tab?).
Just got no idea, what to do now - the only thing i know is: before flashing, i need a open bootloader, but i've got no idea how to do that. The Guide linked in this posts: http://forum.xda-developers.com/showthread.php?t=1622425 is just confusing me more and more
After a reading a few times, it seems to me, that MY next step should be:
"Automated flashing tool" (STEP 5= Going into APX mode see Q&A or use A500 manager)
-1-Reboot your tablet and make sure on your tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
[...]
-It will ask if you are ready (click yes if you are)
Click to expand...
Click to collapse
Is it correct, that THIS will help me to patch/open the bootloader?
Or do i just have to follow this as a next step to create a patched bootloader:
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44 ?
voodoo441 said:
Well, it seems it's not just you being dumb ...
I tried the same - original OTA 4.0.3 and rooted my A500. Now tried to use the 'AfterOTA'-Tools, but getting stuck in step 3 of 4 (maybe i just need to insert a SD-Card in the Tab?).
Just got no idea, what to do now - the only thing i know is: before flashing, i need a open bootloader, but i've got no idea how to do that. The Guide linked in this posts: http://forum.xda-developers.com/showthread.php?t=1622425 is just confusing me more and more
After a reading a few times, it seems to me, that MY next step should be:
"Automated flashing tool" (STEP 5= Going into APX mode see Q&A or use A500 manager)
Is it correct, that THIS will help me to patch/open the bootloader?
Or do i just have to follow this as a next step to create a patched bootloader:
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44 ?
Click to expand...
Click to collapse
Hi voodoo, no, neither of you are being dumb!!! It CAN be a complicated procedure, we try to make our guides 'simple' but theres ALOT that can go wrong
Yes the last link you posted will flash the patched bootloader!!!
- but basically this is what SHOULD happen
Note: The only way to get a custom ICS rom on your tab is with the v8 bootloader by skrilx_cz. This must be flashed via nvFlash/apx mode.
Note:The only way to install a custom recovery like cwm or twrp etc is with v8 bootloader.
Note: You cannot use Acer Recovery Installer unless you have the v8 installed.
Note: Rom Manager does not support our Acer Tabs...please don't use it to flash 'anything'!!
OK heres an overall view of the process:
1. Install Acer and adb/fastboot drivers
2. Retrieve your CPUID...
3. ...and use it to generate your SBK
4. Download your ICS or JB rom and copy to your sd card (internal or external)
5. Enter apx mode to begin the flash!!! or use apxFlash tool
5. Use balckthund3rs apxFlash tool and follow the instructions: hint: dump and save your bct!!!
5. If using civato's manual nvFlash method - Put your tab in apx mode and run the .bat file
5. AfterOTA Tool is only for those tabs which have OTA'ed to ICS!!!
The main issues you will have with the actual flashing process itself is a partitioning error or a bct error - and both of these are easily fixed...UNLESS your tab in one of the few with a hardware fault which only a new motherboard can remedy
Once you get the big white "PASS" on your tab, boot straight to your new custom recovery, do the FULL WIPES and flash your new rom....DONE!!!
Well ... i now used AfterOTA - but not in a virtual machine - now just natively installed on my macbook via bootcamp (windows). Worked. I now have a V8-Bootloader (the tab shows me this when iam booting it up).
Whats the next step to flash a new ROM? Iam ready to do that? Or is there any other step needed by now?
Regards, Tom
Edit:
I now just tried flashing a custom rom - so i copied the *.zip to my USB-Stick (FAT32) - because i read, i can use an USB-Stick as an micro-sd card.
Tried booting into recovery-kernel - worked for me, but the only thing i can see: a lying android with an red sign ("!").
Did i something wrong?
Oh dear....if u had a stock rom on there then its overwritten
your newly flashed recovery....you need to delete or rename
the "boot.p file" in /system..then reflash the v8...
The very next step should be to enter recovery and flash your
desired rom....
So, it now just works everything.
Used Acer Recovery-Manager to re-flash the recovery - worked fine for me.
But: i tried several 4.1 and 4.2-ROMS ... is it correct, that there's no Google Marketplace anymore on 4.1 and 4.2?
Hi,
I had edited my build.prop and it bricked my pad. I was told to look for a kernel with aroma file manager. Unfortunately, I can't seem to find one that's for the Verizon SCH-i815 version. I would chalk it up to my inexperience, so i was hoping someone could help me.
Just to be clear, I'm not looking to have a custom rom on my pad, I just want to get it back operational. I have odin on my pad itself, so i'm just looking to flash a tar, then use CWM to fix my build prop by restoring the original version.
Were you running ICS or Honeycomb? Either way, it seems that if you can get into download mode you can flash recovery with Odin and then a stock ROM. You might check the i815 summary thread:
http://forum.xda-developers.com/showthread.php?t=1760587
Or the i815 ICS thread:
http://forum.xda-developers.com/showthread.php?t=1932597
Thanks for the links, i'll read up and see if that solves the problem. I was running the stock honeycomb as verizon hadn't yet updated the tablet yet, though they are supposed to soon.
Kralik said:
Were you running ICS or Honeycomb? Either way, it seems that if you can get into download mode you can flash recovery with Odin and then a stock ROM. You might check the i815 summary thread:
http://forum.xda-developers.com/showthread.php?t=1760587
Or the i815 ICS thread:
http://forum.xda-developers.com/showthread.php?t=1932597
Click to expand...
Click to collapse
okay, so i have honey comb on the device, and i'm fine with that honestly, i looked through the first thread, but did not see anything there that mentioned aroma (which I was told to look for since i can't boot beyond Odin). Do you have any recommendations both for a file to download and a method?
Basically, my pad will charge and you get some sort of "response" when you power it on and plug it into a pc. I can enter odin mode by pressing power and volume button, but that's it. I'm just trying to get it back, i don't really care if i have to wipe all the data on there or not, but obviously it would be cool if i did. The way this happened to me was that i edited the model name in the build.prop file after seeing some tutorials on it. There are obviously a ton of tutorials on this, but i've tried several to no avail.
Perhaps someone with more expertise can step up, but I'm pretty sure that if you flash a rom it overrides your build.prop?
All you did was change the build.prop, right? If you can connect with adb, I'm thinking you can probably copy over a build.prop to replace yours.
Sent from my SCH-I815 using xda premium
yes, that's all i did. I don't have any experience with ADB, though i'm not scared of command line ... just have never used it at all. In looking at something like this: http://tabletmods.blogspot.com/2012/06/modifying-buildprop-in-pc.html my concern would be that there's no way for me to put it into debugging mode. Any thoughts on that would be appreciated
helpermonkey said:
yes, that's all i did. I don't have any experience with ADB, though i'm not scared of command line ... just have never used it at all. In looking at something like this: http://tabletmods.blogspot.com/2012/06/modifying-buildprop-in-pc.html my concern would be that there's no way for me to put it into debugging mode. Any thoughts on that would be appreciated
Click to expand...
Click to collapse
Did you try? Maybe it is in debug mode? Would you find your build.prop.backup with ADB commands?
However, if you do things you do, you need to have a backup
So flash another kernel and you will have a cwm. Not sure but I think in cwm you should have an option to activate usb-debugging...
md p9516 - root -waiting for cwm -- thnx2all
Hi there,
I have only had a little bit of time to address this over the past few weeks but i'm hitting brick walls everywhere I turn. At this point, I just want to restore my tablet to stock. I am not entirely sure why this is so incredibly difficult, but I cannot find a method that seems to allow me to replace my backed up build.prop. So meanwhile, I helped a friend out with a bricked nexus 7 using the nexus root toolkit, is there anything like this for the galaxy tab?
To clarify:
I had a rooted galaxy tab running 3.2 from Verizon. I edited the build.prop and it ended up bricking my tablet. The only option is to boot into recovery, at which point I'm presented with volume up (continue) or volume down (cancel). If i hit up, i'm taken to ODIN MOode, where the product name is listed along with binary (samsung official) and custon binary download: no. That's all i can do.
I downloaded CWM recovery from here: http://forum.xda-developers.com/showthread.php?t=1542897 and followed the instructions here: http://theunlockr.com/2012/11/14/how-to-install-clockworkmod-recovery-on-the-samsung-galaxy-tab-7-7/
however, when i subsequently try and boot into recovery mode, i have no luck. It does not seem to "take" the update thus i'm left with odin mode on the tablet.
!
i think - wrong area to ask...
Hello all, when I try to use the SD update I get the upright Android with the green bar below & within a few seconds I get the dead Android with a red exclamation mark above his chest. Does this indicate a hardware fault or should I keep trying different update files? Thank you, hoz
thehoz78 said:
Hello all, when I try to use the SD update I get the upright Android with the green bar below & within a few seconds I get the dead Android with a red exclamation mark above his chest. Does this indicate a hardware fault or should I keep trying different update files? Thank you, hoz
Click to expand...
Click to collapse
If you have the correct update.zip you should be fine.
If you're trying to fix a brick you may need to use nvflash.
dibb_nz said:
If you have the correct update.zip you should be fine.
If you're trying to fix a brick you may need to use nvflash.
Click to expand...
Click to collapse
I've downloaded the OTA TOOL & am trying to download Acer APX/Fastboot/Recovery Drivers but the link in Where's my CUPID no longer works. I plugged my a500 into my laptop in fastboot mode but it could not find the drivers either. Any idea where i could find them? Thank you very much for your help.
thehoz78 said:
I've downloaded the OTA TOOL & am trying to download Acer APX/Fastboot/Recovery Drivers but the link in Where's my CUPID no longer works. I plugged my a500 into my laptop in fastboot mode but it could not find the drivers either. Any idea where i could find them? Thank you very much for your help.
Click to expand...
Click to collapse
If the rom you had on there was a Stock rom you OTA'ed, then afterOTA tool is the tool to use to Update the bootloader....you are soft-bricked so none of the tools are much use to you.
Which link in the CPUID guide does not work pls, I shall fix that. Try the one in the root guide in my sig.
If you are not currently flashed to skrilax_cz unlocked bootlader, fastboot will not work.
You're really best to start at the beginning in trying to unbrick.
This means downloading everything you need BEFORE you start.
That means:
Acers website for the acer drivers.
The root guide for the adb/fastboot drivers.
A rom to flash ICS, JB or stock rooted ICS.
The babsector.rar file to unbrick you.
You need to know how to get your tab in apx mode manually.
You also need to run the flash manually. Use the babsector file for that and post any errors you get.
Read thru the root guide in my sig, and make sure you have some understanding of what you're about to do. It makes it a lot easier to have all your files downloaded. The actual flashing process takes about 5 mins.
The babsector file will reset your tabs partitions, flash a recovery so you can do the formats and wipes before flashing your rom. Also installs the v8 unlocked bootloader.
dibb_nz said:
If the rom you had on there was a Stock rom you OTA'ed, then afterOTA tool is the tool to use to Update the bootloader....you are soft-bricked so none of the tools are much use to you.
Which link in the CPUID guide does not work pls, I shall fix that. Try the one in the root guide in my sig.
If you are not currently flashed to skrilax_cz unlocked bootlader, fastboot will not work.
You're really best to start at the beginning in trying to unbrick.
This means downloading everything you need BEFORE you start.
That means:
Acers website for the acer drivers.
The root guide for the adb/fastboot drivers.
A rom to flash ICS, JB or stock rooted ICS.
The babsector.rar file to unbrick you.
You need to know how to get your tab in apx mode manually.
You also need to run the flash manually. Use the babsector file for that and post any errors you get.
Read thru the root guide in my sig, and make sure you have some understanding of what you're about to do. It makes it a lot easier to have all your files downloaded. The actual flashing process takes about 5 mins.
The babsector file will reset your tabs partitions, flash a recovery so you can do the formats and wipes before flashing your rom. Also installs the v8 unlocked bootloader.
Click to expand...
Click to collapse
The link under DRIVERS: Acer Support for Acer APX/Fastboot/Recovery Drivers. Just loads a Acer error page. I get the same error page when using the link in [GUIDE][ICS] Beginners Guide - Rooting, Flashing, Unbricking.
I downloaded the OTA tool to get my CUPID, tried blackthund3r A500 manager but I need BUSYBOX installed. What would be the easiest way to get my CUPID?
About 3 months ago I bought a manufacturer refurbished motherboard from the States (I'm in Australia) had my local PC shop install it, been working great. The other night it froze & I turned it off & then back on & its won't boot past the acer screen. It's stock, I haven't modified it in any way.
i have iconia a200 got brick
I think I'm having issue with the adb and fast boot drivers..not sure it they are installed. My tab only boots into apx mode. It will launch to bootloader mode while trying any of the tools. .but hands mid way. Doesn't seem the tools see it correctly because no atx devices are detected. The acer picassa driver goes I'm because I see the tab pop up. .but not sure the other drivers are right. So I'm stuck.
Sent from my SCH-I535 using Tapatalk