i was just using my nexus perfectly it was running 2.3.6
i wanted to root... i'm guessing i used the wrong method
i used super one click... idiotic move
the phone is constantly rebooting
i've unlocked the bootloader and i used bextboot...
anyone know how to fix this?
thanks in advance!
root
i feel your pain ,i really do 'cos i have just gone thru this process two days ago!.
if you follow the guides below ,you should recover your phone as i did.
VAIDUS SIRTAUTUS BLOG --google it 'cos i'm not allowed to post links ...Yet
good luck and remember to back up your data BEFORE you start!
dennis
Can you access recovery? press trackball and power(same time) if it gets you to the 3 androids on scateboard i think youre all good, proceed to recovery and just flash the stock image link here http://forum.xda-developers.com/showthread.php?t=1012382 then try to root again gingerbreak would be be a good choice.
thanks... now i'm just having one issue
i want to flash the cool3drhyme mod, it keeps rebooting though
i flashed it through clockworkmod
i feel like i'm doing something wrong
i created the EXT4 partition using mini tool partition before flashing
after that it just stayed on the screen for like 10 min
so i formatted my card completely to fat32 and flashed again and it keeps rebooting
i feel like this has something to do with the EXT partition
Did you read OP page and last dozen or so pages of thread for tips, info etc
It requires 1gb ext4--I have had no problems with ext3
Sense roms are big--I use 1.5gb 0 swap
Repartition outside of phone like you did, do a full format not quick--I like sdformatter
Not sure on your recovery--but you need to wipe System/Data/Caches/etc
Some boots do take awhile for Sense roms--RCADS took 14 minutes on initial boot
If too long just pull battery, sometimes it will boot back up fairly quickly
Be sure to always wipe data and cache when installing a different rom. (Not upgrading the same rom, then it's okay not to wipe data, but wiping cache can help)
It truly boggles my mind when people use an unlock method OTHER than the one BUILT IN TO THE PHONE!
And then they're surprised when it doesn't work. -_-
and created a special patch to run the full wape used the recently
Hey every1,
i got weird problem with all ics roms, even SD <
I can successfully install tytung beta1 rom and run it, but beta2+ roms and similar ones, and SD build all have same thing:
i have random freezes/stuck at bootlogo(it doesn't freeze, it simply continues to do the animation forever), only ONCE it booted, but since i needed kernel fix(for headphones) to apply - i restarted, and wasn't able to boot in successfully again. Now almost all the time i get freeze/reboot after ~5-10sec after i get into ics rom, SD build doesn't boot at all.
Partitioning problem? - have tried many partition layouts.(like 190/10,200/10,210/10,200/20,230/20,210/20 and so on, also with different bootloader partition size up to 8mb)
Also i have always used task29 and fully wiped everything and reinstalled from scratch, still didn't helped.
Also tried to boot with plugged in usb cable/without it or with/without memory card in.
Maby it's radio version problem, or don't know, what else can cause the problem?(radio ver:2.15.50.14)
Between i have created big cache/memory sometimes(up to 250mb partition/44mb cache) - and still it didn't worked fine :/ also tried different clockworkmod versions(3.0.0.5 and 5.something), magldr 1.13
p.s. i have europian hd2(not t-mobile)
or maby i'm partitioning it wrong? i change partition sizes inside flash.cfg and after i flash clockworkmod(i do task29 before that, and install fresh magldr), maby i should change somewhere else/more?
Also formatted memory card many times(sdformatter) and redownloaded roms, still same result.
p.s. tried ~3ics beta2+ roms(not sure mb even more), and 1sd rom
Edited:
forgot to mention, when phone kinda freezes(the boot animation/startguide for ics) - when i press physical buttons - the backlight appears and after that dims away as it does on every other android rom, so it kinda feels that rom isn't frozen, only the screen. Also sometimes after getting ics welcome screen - after ~5-10sec it gets back to bootloading animation and does it over and over again...
hey
I'm having the same problem did you figure it out I'm having same problems with ics and cm7
What has worked for me is 5/230/5. Im using tmous but that layout should work for your version.
Thanks
You are the man bro I cant believe it was something so simple
problem
I just tryed that partition it worked then rebooted while i was trying to set up the device do you know why?
Youngmyster said:
I just tryed that partition it worked then rebooted while i was trying to set up the device do you know why?
Click to expand...
Click to collapse
I am using the ICS beta 3 now, I have updated with every release and I didn't get this problem. It sounds like something crazy, you may just have to wait a little bit because ICS is still very beta... Check out HD2 Toolkit as well it makes it much easier flashing..
Wait, I didnt didn't see that you were having problems with cm7.. :-( I'm afraid I just wasted your time on my reply..
What Clockworkk mod recovery are you using?
And how are you transfering your data to your SD card?
---------- Post added at 05:15 PM ---------- Previous post was at 05:07 PM ----------
Try backing up your entire SD card, and then reformat it completely.
Then task29 and wipe everything.
I think you said you use magldr, since your having these problems try cLK
Use just a simple 220MB 5MB cache on HD2 Toolkit
Install ClockworkMod Recovery 5.0.2.6 as it is the newest one.
Transfer your zip file to your SD card using a card reader.
Install and see if ICS will boot.
Try that and see if it works. It should work.
Question. Do you have this same problem with any roms besides CM7 and ICS?
---------- Post added at 05:17 PM ---------- Previous post was at 05:15 PM ----------
Don't forget when using cLk you download the main zip file for the rom, and then a separate zip for the cLK kernal..
Sorry for the new thread, but I can't post in the dev section yet - this is really a follow up to http://forum.xda-developers.com/showthread.php?t=1258855 - maybe someone can move it?
I just used the following zip file and it worked well:
CM Nightly 257 Version (Upgrades from Gen1 to Gen2 & installs latest CyanogenMod nightly build - all in one)
Download: cm7-n257-blade-gen1-to-gen2-tpt.zip mirror
Download size: 107.8 MB
MD5: 813ba810ca0a596da4eb6ea7e47205a1
SHA1: 11030dff7b48c79463185b25fc848d488fe77768
A couple of things that weren't clear from the Instructions section (which presumably apply rather to the non all-in-one versions - haven't tried personally) were
a) Does not "reboot into ClockworkMod recovery", rather direct into CM Nightly 257, and
b) Wipes data - presumably must have done because the boot into CM was successful.
This is all very good and nicely automated; could just amend the instructions to be something like:
It should take a few seconds to flash the new Gen2 firmware (you should see some green text), then it should either reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom (for the custom and stock versions), or reboot into CM Nightly 257, no need to wipe or install the CM rom oneself (for the all-in-one).
All in all a great piece of work.
New here and also wish i could post on that thread as i found it extremely useful and it persuaded me to make the jump and finally upgrade my San Francisco.
It honestly feels like a new phone now, after running stock orange 2.1 since i got it about 10months back with some tweaks to launcher etc. I wish id done this a lot sooner. I also used the nightly 257 rom.
I was also (initially alarmed!) a little confused about the points a) and b) you raised above as mine also seemed to skip those steps and just launch straight into the mod. All well and good though this has now left me wondering if the step b was vital. Prior to this on a fresh start and after using Advanced Task Killer to kill all the crap id be looking at around 300mb free memory. Since the new ROM i now have 173mb free in Advanced Task Killer. Odd since i dont have a fraction of the amount of stuff on the phone considering all the stuff that came preloaded with Orange etc.
I dare say the new OS may have a larger footprint. Though my main concern is that as I somehow skipped the part where it says
"then it should reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom." I wonder if this means not all the old ROM has been erased and results in my limited memory.
If i check under Settings > Storage it gives me 294 Total with 203 free under internal storage. Wish id thought to check this value prior to install...
That aside it all works great and im delighted with it.
OK, what do you want free memory for? You should realise that is memory that you have paid for which isn't in use - wasted memory in other words. Android 2.3 uses more ram, when nothing else wants to use it, in order to make your phone run faster, that is a good thing. If you want to use an app which requires a lot of memory then android will free it automatically.
Don't use task killers, they harm system performance by working against Android's own memory & task management system (which is better than any task killer), reduce battery life, cause bugs & you wont get any support at all from anybody involved with Cyanogenmod if you use one.
The all in one version that includes a rom starts straight into that rom, that should be pretty obvious.
It will wipe your data, if you're updating from Android 2.1 then it'll wipe everything. Otherwise it'll miss any apps on your sd card, that's the only reason i say to wipe data - if you're coming from stock Android 2.1 then you can't have any apps on your sd card, so it makes no difference.
Stock Android 2.1 phones have 207mb internal storage ( /data) in total, you gain almost 90mb. The stock Orange bloat apps use up more room (dalvik cache) too, so you end up with much more room to install your own apps & games.
Unable to convert Gen1 -> Gen2 via TPT
Hi all,
I didn't want to start new thread, so I'll post here. In short - I'm unable to convert my Gen1 Blade to Gen2 using wbaw's TPT method.
I followed instructions carefully, tried 2 different zips (Gen1-to-Gen2-TPT-v10-custom, cm7-n257-blade-gen1-to-gen2), used 3 different microSD cards (1GB, 2GB, 8 GB class 4) and still nothing.
Image folder is on the card, all MD5s do match, I turn off the phone, wait few sec (I even took the battery out few times), press and hold menu&vol+ and then power, red power led is on, then green robot shows up, and... nothing, no green text on the screen, just few seconds later my Gen1 ROM is booting.
Any ideas?
make sure that you keep holding menu & vol+ when you press power. that's the only thing i can think of, unless your phone is already gen2. a few sd cards dont work with it, but it shouldn't be that hard to find one that does.
Thanks for the answer, wbaw.
I am holding both - menu (the one in the middle, between home and back) & Vol+ - then I press and hold power, after few seconds I let the power go but keep holding the other two. After few another seconds (while green robot is visible) a regular boot animation shows up.
My phone is definitely Gen1, as I recently installed G1 ROM (mmhmp) and previously used Mr. Pigfish, both report Gen1.
I just reformatted my stock Transcend 2GB card in CWM, put only 'image' folder with all files (MD5s are ok) and still no go. What the hell?....
Btw. I'm using 3.0.2.8 CWM. Does it make any difference? I'm running out of ideas.. what else can I check?
No idea then, sounds like you're doing everything right. The flashing should happen before the green robot shows up, if the robot comes up straight away then it's already failed to flash anything & you have to try again. It's a zte flashing program, built into one of the first bootloaders (the green robot is displayed by a later bootloader), you need to be holding vol+ & menu when you turn it on & for about a second after that, then you can let go. You should see some green text, or maybe just a black screen, then after a minute or two a big version of the green robot & clockworkmod 5.
Clockworkmod is irrelevant, it's a different zte flashing process.
Only thing I can suggest is try another sdcard. I know a few people have reported it didn't work with their sdcard, but it was only a few people & it worked with the 2nd or 3rd sdcard they tried. I got a verbatim 2gb with my phone, that works, sandisk 8gb class 2 works too & so does my new 16gb class 10 verbatim.
If everything fails & you must update to gen2, then there are some windows software phone update packages that let you update your phone using your windows pc. Those packages & instructions are in the zte blade section at modaco.com. It's a bit harder, slightly riskier, but hopefully it'll work.
I just tried another card, some noname 512MB from my old Nokia (I didn't even realized I have so many microSD cards...) and unfortunately this one is also no good. Damn....
So, TPT is built-in and should work with all Gen1 ZTE's no matter what ROM or CWM I'm using, right? Is there any possibility I accidentally removed/erased or destroyed part of it?
I didn't even flash that much, from stock Blade (well, I removed simlock), I installed CWM and went to Swedish Spring (half a year ago). Now I've decided to move forward, installed Gen1 MMHMP, but decided to give CM a try. As you can see not much of a history, therefore I'm even more surprised TPT is not working in my case...
Is there a way to tell this flasher actually works? Something other than just putting gen-to-gen converter image? Any troubleshooting you may think of?
Edit: Tried another card (that's already 5th card!!), 8GB class 4 - no go... I don't think it's a problem with microSD card anymore... it has to be something else.
It turns out TPT is not available on my Blade (some European versions lacking TPT were reported). Anyway, I have successfully converted to Gen 2 using Windows/FTM method. I didn't find it hard, it's just a bit more hassle with repeated flashing. All went good, no need to fear.
Thanks!
Hi, sorry to thread hijack the thread hijack, but I too have a question about this process and can't post in the dev forum.
I just followed the all-in-one process on my girlfriend's brand new stock Orange San Francisco, and it worked flawlessly. I'm now wanting to do the same to mine, but it isn't stock; it has ClockwordMod (3.x, I think) and a FlibbleSan ROM from Modaco installed (Gen1).
What (if any) different steps do I have to take to get everything rolling on my own device? Apologies if it's a stupid question, I was just spooked by the parts about not using it on operator upgraded 2.2 devices and wondered if the same disclaimer applied to user updated phones.
(Merry Christmas )
Never mind, I took the plunge and everything works fine.
Random Reboots after Upgrade
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?
eddiem74 said:
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?
Click to expand...
Click to collapse
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app
karthiknr said:
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
No, just done the update?
Sent from my Nexus S using XDA App
eddiem74 said:
No, just done the update?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You did a wipe before flashing right?
Sent from my Blade using XDA app
karthiknr said:
You did a wipe before flashing right?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App
eddiem74 said:
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Sounds like you need to calibrate the proximity sensor. I think there should be a ZTE Blade settings app that you use to do it.
Probably better to flash one of the latest self-compiled versions of CM7. Its been a while since nightlies were made, but lots of new stuff has been added/fixed since 7.1.0 RCs/stable.
eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Like Amphoras says calibrate your proximity sensor in the ZTE Blade Settings app. That should do. If you still have a problem,flash the 257 nightly or any other ROM if you don't like CM.
Sent from my Blade using XDA app
this might be a bit offtopic but is there a way to tell from the packaging if the phone has amoled or tft? I suppose tft is best?
Hello Community!
I just got the Defy for my mother, and I am currently trying to put Miui on it for my mom. This one: http://forum.xda-developers.com/showthread.php?t=1161110
I'm currently stuck right now... I was able to flash using RSD lite the nordic 2.2.2 sbf (3.4.2_177,) but whenever I put an SD card into the phone I'm stuck waiting for it to boot.
Please don't say "first boot takes a long time." I went to work and worked 9 hours and left the phone on waiting for it to boot... It didn't boot. I really hope that the first boot isn't supposed to be longer than 9 hours.
Not having an sd card prevents me from downloading any apps from the market (2nd init) or even putting CWM on the phone...
I've tried to ADB push, but whenever I try it, it says "fail" because of "read only."
I then try "adb shell sysrw" and that doesn't work either...
I've tried the T-Mobile SBF and the UK SBF, they both boot, but once the SD card is in. No go.
Can anyone offer any help??
Thank You,
lilhugo
edit: I forgot to mention I've tried 4 different micro sd cards, 1 2gb class 2, 2 8gb class 4, 1 32 gb class 10 and they all read perfectly fine on my Sensation.
By it didn't boot, I mean that it was stuck at the M logo forever.
First suggestion: wipe data and cache using stock recovery.
ejstubbs said:
First suggestion: wipe data and cache using stock recovery.
Click to expand...
Click to collapse
I've done that. It din't help. =/ I also used the format/factory reset from stock recovery too.
I'm curious if I would be able to any of the Gingerbread sbfs and use that MIUI rom. Anyone know?
it can sill work if you update your bl to version5(GB2.3.4,NOT2.3.6),so you could try to flash GB SBFs.
Tim_Pan said:
it can sill work if you update your bl to version5(GB2.3.4,NOT2.3.6),so you could try to flash GB SBFs.
Click to expand...
Click to collapse
Okay I'll try that. Thankfully the person I bought this phone from kept it bone-stock... I'll report back if doing that helped.
Hey everyone, I've spent the best part of today trying to flash Sense ROMs and every time they won't boot. Just wondering if there's a minimum SD Card size you need to use or something like that, as even after a Task 29 and full reinstall of magldr, recovery and radio I keep getting the same errors
I'm using the 2GB SD that came with the phone and putting 1024MB of that into an SD-ext partition using recovery. I also have a 250MB recovery partition (above the minimum needed).
I can get it to boot up to the bootanimation but that's about it. So far I've tried AndroPlus (boots to a black and white screen which reboots my phone), Energy ROM (runnymede port, gets to a bootanimation and stays there indefinitely - I've left it about an hour with nothing at all) and TeamBlueDroid's runnymede port (which won't boot at all).
I also have a problem which means any MIUI rom wont boot and GB ROMs won't use my data connection because I'm a UK T-Mobile customer and T-Mobile are sharing their 3G signal with Orange, which my phone doesn't like
So I'm left with CM9 which I've just re-installed which is now stuck at the GO GO GO! screen on magldr... Even when it does work, the battery drains in less than half a day
If anyone can help with any of these things PLEASE tell me!
THANKS!
In my opinion i think you need a bigger sd card. Also you need to make sure you have the correct partition. If the rom asks for a partition of 5/330/8 the you need to have that partition, not 5/330/5. The rom WILL NOT BOOT if it isnt correct all the way through.I hope this helps
---------- Post added at 07:02 PM ---------- Previous post was at 06:42 PM ----------
one more thing...make sure you read the instructions for each rom completely. certain roms ask for sd-ext of 2/3/4 just for the rom to work correctly and to have enough internal memory for the rom to run correctly
Ah thanks very much! I think that might be where I'm stumbling, because I do set 2 of those partitions to the right size every time using the NAND toolkit, but I never see an option to change the boot partition. I'll look into it and see what I can do, thanks
Also yeah I think I'm going to buy an 8GB SD card, but the problem is I'm going to be upgrading to an HTC One S in a few months so it'll be redundant then, so I was trying to hold off buying a new card... I guess if it has to be done then oh well
You can open a recovery zip file with notepad and adjust the partition as needed per rom. this cannot be done with hd2 toolkit. 8gb card is only 15 bucks at walmart...get one! its always good to have a few lying around