Scroll Engage - wrong ROM flashed. - Upgrading, Modifying and Unlocking

Hi,
I don't know if it's a proper place for this, so sorry if not.
I have (or had) android tablet "Scroll Engage" from storageoptions.com. It was slow as hell so i decied to put there cyanogenmod. I couldn't find dedicated one, so i've try with the rom here: http://forum.xda-developers.com/showthread.php?t=1821398
The rom itself installed without the problems, but after booting it the touchpad was not working ... so i've decied to try patches from same site... i don't have much knowledge about android, so i started to check one after another .... and at some point one of them replace gpu drivers with the wrong one, and after couple more boot was overwrited ... so now i can't see anything on the screen, and even when i boot device with vol + power i can't see device with adb (but windows see that device is connected)... so my question to you guys ... is there anything i can do, or i can use it as a glowing flying disc?

Related

htc desire doubt about installing rom

hello. im buying a desire tomorrow and i have some doubts.
can you give a link with some guide to install some new rom into desire?my previous phone was a samsung i8910 and almost every week i was instaling cooked roms but in android the process seems a lot different. i've seen some cool roms but i dont want to screw up the phone. i'm running windows 7 64bits. hope that's not an issue. thanks in advance
Follow this instruction to root and flash custom roms:
http://android.modaco.com/content/ht...-1-21-support/
In the beginning of that process you need to make a gold card, instruction can be found here
http://android.modaco.com/content/ge...ng-a-goldcard/
After everything is done, you should be able to flash whatever (compatible) rom you want. My recommendation is this
http://android.modaco.com/content/ht...nline-kitchen/
However, you must take note that there's some random USB bricking going on when flashing roms now.
You might want to have a look at this thread here.
Personally, I feel that flashing with Linux is more stable than using Windows.
I started rooting with Windows 7 and some problem occur halfway through the process.
I rebooted my pc to Ubuntu and continue the rooting process and everything went well.
I did everything on my desktop with 64-bit Windows 7 without any problem.
problems after installing custom rom on htc dsire
*
Hi there I’m even scared to write…
Newbie Noobie here. Greetings!
Got myself a birthday present a few days ago – HTC Desire.
If it helps, here are the details:
======
Firmware version: 2.2
i rooted my phone and then followed the steps to install custom rom
Anyway, here’s my problem (there were posts about it before as well).
Once I reach point 5 in Step 2 [i.e. Turn off your phone & turn it back on holding POWER + VOL DOWN then use vol up/down to scroll down to ‘Recovery‘ and power to select.] after I click ‘Recovery’ my screen either stays white with the green HTC logo or just goes black – in either case, that’s it… nothing happens and no buttons work.
The first time it happened I almost got a heart attack (well, which noobie didn’t?) because I thought I’d just bricked my baby… Right now it is still the only way for me to do ANYthing after getting the black screen…
Any suggestions/help will be more than welcome! Thanks in advance!!!
(And sorry for the long post… I always need long intros and all the details listed to make myself as clear as possible)
Please do help me
i am nearly crying while typing it
email me the response
cheers
Raj
rajverma3135 said:
*
Hi there I’m even scared to write…
Newbie Noobie here. Greetings!
Got myself a birthday present a few days ago – HTC Desire.
If it helps, here are the details:
======
Firmware version: 2.2
i rooted my phone and then followed the steps to install custom rom
Anyway, here’s my problem (there were posts about it before as well).
Once I reach point 5 in Step 2 [i.e. Turn off your phone & turn it back on holding POWER + VOL DOWN then use vol up/down to scroll down to ‘Recovery‘ and power to select.] after I click ‘Recovery’ my screen either stays white with the green HTC logo or just goes black – in either case, that’s it… nothing happens and no buttons work.
The first time it happened I almost got a heart attack (well, which noobie didn’t?) because I thought I’d just bricked my baby… Right now it is still the only way for me to do ANYthing after getting the black screen…
Any suggestions/help will be more than welcome! Thanks in advance!!!
(And sorry for the long post… I always need long intros and all the details listed to make myself as clear as possible)
Please do help me
i am nearly crying while typing it
email me the response
cheers
Raj
Click to expand...
Click to collapse
phone info pls
what did you use to root your phone? unrevoked?
you probably have a bad recovery flash, redownload unrevoked and start over again.
(were you able to access recovery before?)
btw it would help if you opened a new thread instead of hijacking this one
regarding to OP
* you must not forget to install all neccessary drivers
i. download & install htc sync
ii. download android phone driver
* I'm using win7 x64 and rooted my phone with no problems (pretty fresh install though...)
* you wouldn't need a goldcard if your phone is not branded by your carrier.
hope this helps

Flashed System Partition with Boot Image - Help I'm Stupid

I would be so greatful if someone could help me, I think I have really messed up.
Coles Notes: I flashed the 4.0.4 image to my System partition which I am pretty sure should have gone to the boot partition now... Holy **** I'm dumb.
Anyways now my phone is just stuck saying Google. Anyone who can point me in the right direction of even a System image I can flash over top I would be so greatful.
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Moleculor said:
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Click to expand...
Click to collapse
Not a dumb newbie, checking if bootloader still works is a good idea
@OP: If you can get in the bootloader, your best bet would be unlocking, installing CWM and then flash a ROM through it.
You can also flash the stock ROM via the GNex toolkit.
Just read the guides and information here in the forums, it seems confusing at first but is really simple once you get used to it.
Good luck!
Thank-you for your quick response. I have CWM installed and can get into the bootloader. the problem now seems to be I cant get the device to show up in windows I always get <waiting for device> when going to flash it. Any ideas? I have been searching the forums trying to find an answer but nothing so far seems to have worked.
Another dumb newbie thing, but when you plug the phone in to the USB port on your computer, does your computer show the phone as having connected (ala the ADB driver in your Device Manager in Windows)?
If not, double check to make sure your ADB drivers are installed. I doubt they aren't, seeing as how you were flashing stuff earlier (from your computer, right?), but it's a wild guess anyway.
Thanks to everyone for the advise. Yes I could see the drivers and they were working perfectly according to device manager. However I guess it was stuck outside of debug mode?
Anyways from the boot menu the program was able to detect it, flash 4.0.4 to the phone, and then I was able to install the canadian radio without issue (hence the reason why I did this in the first place, we are stuck on yakjuux with 4.0.1).
Thanks again to everyone, great learning experience.
Sure thing!
Glad it worked
As a future reference, the "Boot Menu" is actually where you need to be for flashing via PC. The commands won't come through if you're in recovery.
Make sure to make an Android right now!
You enter CWM Recovery, go to backup and restore and then hit backup.
In case your phone ever messes up while you're not close to a computer, you can just boot into CWM and hit "restore", it's as easy as that.
I always have 2 recoveries on my phone just in case.

[RECOVERY]TeamWin Recovery Project - TWRP Touch [v2.2.2.1]

Here is TWRP v2.2.2.1 recovery i made from source
Problems:
---When installing ROM or making backup if text goes over screen recovery doesnt go into new line
---Formatting takes ages, if you dont want to wait go to settings and check use rm -rf instead of format, it should give you the same effect
---You tell me
How to install:
---Download the .zip and put it on your SD card
---Reboot to recovery
---Flash the .zip
---Reboot and say hello to your new recovery
Credits:
---TeamWin
---Cyanogenmod (Used their android_device_htc_hero)
---Shelnutt2 (Taught me how to compile something from source)
---My laptop for giving me it's processing power to build this
Download links:
---19.Sep.2012
http://www.mediafire.com/?glxal7xhmokrrln
Screenshots:
I already did this?
But good job anyway
Yes you did, but that was v2.2.2.0 this is latest build 2.2.2.1 and it's built from source, sorry if i offended you
No no its fine
I'm glad you did it
Oh and I may have fixed the CM10 booting problems, but I wont spam this thread about it
jordfaz said:
No no its fine
I'm glad you did it
Oh and I may have fixed the CM10 booting problems, but I wont spam this thread about it
Click to expand...
Click to collapse
Will you please PM me about the way you did it so i can try too, btw i might try to compile CM9&CM10 from source..
Ill pm you tonight if it works, and I can't wait for you to compile CM9/10
jordfaz said:
Ill pm you tonight if it works, and I can't wait for you to compile CM9/10
Click to expand...
Click to collapse
Well i cant wait either, but im not that sure i can compile CM10, but CM9 i think it's doable
Did you managed to port it ??
Ye its on my Github, its in my signature, just zip it up and flash, havnt tested it yet though.
jordfaz said:
Ye its on my Github, its in my signature, just zip it up and flash, havnt tested it yet though.
Click to expand...
Click to collapse
I cant test it either, my Heros touchscreen is messed up, shows input even when im not touching it, im gonna try to fix it so i could continue development, btw can you PM me about the way you ported or you compiled from source
hi, kemoba,I've got problem here.
I flashed your TWRP touch recovery from CWM, booted into recovery everything works fine. Then i flashed the MTD zip file for CWM ( so stdupid~), which makes my hero bricked: I can't get into recovery mode since it was broken by flashing the MTD file, and can't boot into android system since the system is MTDed.
would you tell me is there some way for me to use adb command again? I think it is the only way to save my hero. Thanks.
Are you S-OFF-ed, to check power off your phone, unplug battery then replug battery, hold VOL-DOWN (vol=volume) + POWER, you will get a white screen with 3 scating androids, and the first row will say something like HERO CVT ENG S-ON or S-OFF. Second thing is, did you try to boot into recovery by powering down your phone then unplugging and replugging battery, press MENU+POWER at the same time and leave it pressed until you boot into recovery, it should boot into recovery after 30 secs to a minute if it doenst work hold it a bit longer just to make sure you cant boot into recovery. BTW, what MTD file did you flash, do you have a link to it ?
Actually it's HOME+POWER to boot into recovery, my bad
Hi, kemoba, thanks for replying. VOL-Down+power or HOME+Power or Back+Power didn't take me to the Hboot or recovery or fastboot, actually only a HeRO logo appear no matter which combination of Power key and some other key(except the vol-up+power one ,this makes three times shake and nonthing) . In short, I can't get into any supper mode, and feel hopless... BTW, ubuntu is my pc system, driver should not problem, and no matter which way to power up my hero, "lsusb" doesn't show up my phone, and "adb devices" shows nothing as well.
Here is the MTD file link:http://forum.xda-developers.com/showthread.php?t=1370963&highlight=mtd
Sorry for my bad english describe.
Any suggestion would be great, thanks very much.
Ummm, VOL-DOWN + POWER didnt take you anywhere ? Im sorry but i think you bricked your HBOOT, when your hero logo showes does it say anything like FASTBOOT USB at top left corner ??? And did you unplug and replug your battery when you tried VOL-DOWN + POWER
So sad to hear that. Volume-down+Power doesn't work, nothing appears but the hero logo. Is there some other key combinations to try? BTW, how to make hero communicate with PC if HBoot and recovery are broken?
Sent from my Transformer TF101 using xda app-developers app
JTAG is the only way, it is a tool that flashes stuff directly to nand memory, you will need to take apart your phone and solder some connections, not to mention you need to get a JTAG module and a JTAG flashable package.. BTW, do you get FASTBOOT USB on top right part when the HERO picture comes
I knew JTAG when i played with my modem some years ago, but since my laptop doesn't have any COM port, i have to send my phone to the repair shop. And only HERO picture appears no matter which key combination pressed, no "FASTBOOT USB" comes out. But thank you all the same.
BTW, TWRP touch recovery is good, great job. I will continue to use this recovery when i get my hero fixed.
And hey, will you take a look at the MTD file? can you port it to your recovery?
I will try to do it, just dont wanna brick my Hero, but im S-OFF so i should be fine, im glad you guys like TWRP you can check out Jordfazs version too. Its a bit older but i think it's less buggy Ill try to fix these bugs and also next version should include my ICS based theme.
Sent from my Hero using xda app-developers app
I get an error while flashing. says
E:Wrong digest: META-INF/com/google/android/update-script
E:Verification failed
any way to fix this and be able to flash? i'm getting this for every rom as well

[Q] Need help / Advice possible Brick :D

So, hey guys, i've used this site a lot in the past, but now i need some help / advice, so i've registered. The following isn't going to be pretty but i'll explain it as best as i can.... infact, i can paste the email i sent to Sony asking for advice, it was this morning, i don't know if they operate or care
Hello people at Sony, my stupid head appears to have bricked my Xperia Arc S Android phone, it was still under warranty until i decided to unlock the bootloader, then i was having trouble restoring it back to stock android, this resulted in me trying to lock the bootloader. But alas, nothing now happens except a lonely green light flashing every so often, if i hold down menu, a blue light appears, which is charming, but then it dissipates and im left lonely again. With just a bricked phone and little dignity.
What are my options, by rules, it's void of warranty, can it be fixed? Can i pay for it to be fixed? Will my Natwest Insurance cover it on the grounds of Accidental damage (My stupidity) and Breakdown due to electrical fault, that being, no electrical softwareness is been transitorized.
I decided to go custom due to the wait for the Xperia update for my phone, out of the 273 S-I variant versions of the Arc S, 246 have gotten the update, but not mine, months had gone by, day turned to night, night turned to day, and i got desperate, i decided to root... for the first time. (And now last)
What i did learn, apart from technology will rise up and defeat us all, is JellyBean works very well to some degree on this phone, HOWEVER, the lack of Flash player caused bad results when playing content, im not sure what piece of code on the JellyBean CM10/Paranoid Android release was rendering it, but if you can get past the lack of flash for this and render images in its mobile bravia engineness then it will work a treat, and i mean it, it really did run well, obviously it was customness, but i digress...
Can anything be done? I do so love my Arc S, and just so you know, if it can't be repaired and I have to change phones, it will still wear the brand logo... Sony Ericsson... and if its your newer phones, that lack Eric's Son, i shall scribe his name proudly across the top with a sharp implement with pride. (With the care of an Adult, or someone equally minded)
Thank you lovely people over at Sony.
Stuart Herrington
Click to expand...
Click to collapse
So, basically it doesnt boot, apart from it does vibrate with button holds and the LED flashes. I tried flashing it with flashtool and stock ROM, but flashtool came back saying it needed unknown sources and debugging mode activated, which makes me think, it could be salvagable and not bricked, however how can i change those settings if i can't get into the phone itself, is there a bypass?
On a side note, i can Hold Menu, plug the phone into my computer and it goes into blue light mode, i cant remember the term for this
but its what i was using for flashboot, you reckon i could flashboot out of this? I was trying so many different methods to try and custom rom my phone that everything got confusing, which was best to use etc, and on another note the phone never booted when i tried to relock it, so im unaware if it finished, it didnt boot at all, and this is the point im at now.
Fortunately i picked up a Xperia U for £135, second hand, actually cheaper than my Arc S second hand, crazy really, but you can see why with the size difference and a couple of small spec differences.
Any help would be appreciated. This isn't obviously the best situation but i'm wondering if anyone has encountered this stupid mistake i've cast upon myself XD
Thanks in advance.
Wait...
I've checked the fastboot status of my phone using Flashtools, and it says my phone needs to be rooted first... hmmm it was rooted, maybe it got undone with the bootloader thing, i guess i can try but i can't access the phone to debugg or allow unknown sources.
Hi Stu15,
The fact that you can boot holding down the menu button is good.
You can probably flash a custom kernel onto your phone this way using the following command.
Code:
fastboot flash boot boot.img
If you have a rom that you want to use, then it usually comes with a custom kernel (called boot.img most of the time) inside the rom's zip file.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
So what you do is copy the rom to your sd card (just plug the card into your computer to do this).
Then flash the custom kernel that came with the rom.
Then boot into CWM and flash the rom (you should clear the cache and the dalvik cache before flashing the rom).
If you don't have a preferred rom, then have a look at this thread - http://forum.xda-developers.com/showthread.php?t=1653188
It has lotd of helpful links, near the bottom of the 1st post are a few roms you can try.
I hope that you come right.
Take care,
Hotfingers
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
stu15 said:
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
Click to expand...
Click to collapse
cool, well done. :good:

[Q] So, I flashed the wrong ROM into my 3HT7G 8.9" Kindle fire. Is there any fix?

[Q] So, I flashed the wrong ROM into my 3HT7G 8.9" Kindle fire. Is there any fix?
I have been googling and searching for years with no usable results and fixes to all manner of problems other than what I have here.
Ok... So a few years back, I was using a program (I forget which one) to flash a new ROM and didn't pay adequate attention to what I was flashing into my Kindle 3HT7G 8.9" Fire. I put the rom for the 7 inch model (Oopse!) Anyways this corrupted the boot sector of the device and now the thing is completely non responsive. I have tried googling every variation of the question I am asking and have tried the hold power 30 sec, Hold power while rebooting, various (unbricking utilities) all with absolutely no results other than seemingly dead screen. I have charged overnight, used factory cable on computer, Voodoo magic chants. (ok so I don't know Voodoo) Kind loving words, Harsh threats, pleading... Etc... The closest to an answer was in some thread somewhere, someone said to another person asking similar question was , "Yep it's now a $200 paperweight..." I understand that rewriting the boot sector to something wrong is stupid. (I presume this is where the information that tells the device who and what it is and what all buttons do resides) I did just that. Is there any way to force feed the correct ROM or even remove the memory to mount in another environment to rewrite it? Is this device really completely useless? Or, is there a way but too cost prohibitive? I have been holding on to this device in hopes that one day a cure can be found and I can thaw it out and perform the required surgery on it.
Thanks,
Dan
alarmguydan said:
I have been googling and searching for years with no usable results and fixes to all manner of problems other than what I have here.
Ok... So a few years back, I was using a program (I forget which one) to flash a new ROM and didn't pay adequate attention to what I was flashing into my Kindle 3HT7G 8.9" Fire. I put the rom for the 7 inch model (Oopse!) Anyways this corrupted the boot sector of the device and now the thing is completely non responsive. I have tried googling every variation of the question I am asking and have tried the hold power 30 sec, Hold power while rebooting, various (unbricking utilities) all with absolutely no results other than seemingly dead screen. I have charged overnight, used factory cable on computer, Voodoo magic chants. (ok so I don't know Voodoo) Kind loving words, Harsh threats, pleading... Etc... The closest to an answer was in some thread somewhere, someone said to another person asking similar question was , "Yep it's now a $200 paperweight..." I understand that rewriting the boot sector to something wrong is stupid. (I presume this is where the information that tells the device who and what it is and what all buttons do resides) I did just that. Is there any way to force feed the correct ROM or even remove the memory to mount in another environment to rewrite it? Is this device really completely useless? Or, is there a way but too cost prohibitive? I have been holding on to this device in hopes that one day a cure can be found and I can thaw it out and perform the required surgery on it.
Thanks,
Dan
Click to expand...
Click to collapse
Hello
I have the same problem.
I have a one idea to connect motherboard witch usb card reader and try to repair my kindle. If i will do that I will writing here all. Or maybe U unbrick ur kindle first or allready u do taht.
Thread moved
Can you go into fastboot mode? Or at least use adb commands.
If not, make sure you have Android SDK
Try my tutorial: http://forum.xda-developers.com/kin...help/kindle-fire-hd-8-9-bootloop-fix-t3137732

Categories

Resources