Database Info

I think I bricked my phone!!

I was attempting to get the Nandroid back up feature going on my phone. I downloaded the recent RC30 for the multi-touch (I couldn't help it), and I was given this error about the application settings not responding and to force quit. Then I downloaded the SPL bootloader and the modified RC30 with the busybox. It's in this post (http://forum.xda-developers.com/showthread.php?t=459830). I did a successful backup, but now my phone won't work right.
When I boot the phone none of the buttons respond until a good 30 seconds into the full boot up, and only after I slide open the keyboard. When I press the power key the screen flashes and the blank wallpaper comes up for 5 seconds. There is no way for me to get into the recovery mode. When I tried that it gives me the phone with the exclamation point.
I think I am just at or 1 day past my 14 days. It's really going to suck if I have to pay for a new phone b/c I got cocky and thought I knew what I was doing. Hopefully you guys have a solution or T-mobile will be forgiving.
Oh, and when I look under settings it says: kila user 1.0 TC4-rc30 so T-mobile will know I rooted the phone and F'ed up.

You could try restoring with DREAIMG.nbh
and you didnt brick it, a brick doesnt do anything, yours sounds like it boots.

I can't get into recovery mode. I can get into fastboot. I found a thread on installing cupcake will help get it back to RC30, but I didn't understand where to type in the prompts.

When I tried that it gives me the phone with the exclamation point.
Click to expand...
Click to collapse
Try Alt-L at this point.

I forgot about that. Thank you! Now I just need to find a way to get my phone back to full functionality. Do I need to just find RC29 or JF RC30 and reinstall as update.zip?
It says "E: Can't open /cache/recovery/command"
We will see if reinstalling RC30 will work. Does anyone have the orignal RC30 that comes installed on the G1? I understand I'll lose root access and that might be the smartest thing for me now.
I reinstalled RC30 and it worked! Thank you guys, and thanks for putting up for my temporary insanity!

I would do a wipe and then update to jf's latest 1.4. But at this point you should be able to update to whatever you want.

Sorry if this is a stupid question but I have made a NANDROID Backup and I would like to know how to restore my phone with the backup I made.

ow to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/show...53&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.

[Q] Idiotically deleted framework-res.apk, bricked my N1

Hi there,
I am such an idiot, I deleted the framework-res.apk from /system/framework/ and rebooted. You all know what had to happen: the Nexus with FRF91 won't boot anymore.
So I am asking for help: Is there any way to restore (i.e. put a stock framework-res.apk) in that folder? I have ADB tools and stuff installed.
Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Of course, I'd rather not delete my apps and stuff but still better than a bricked phone.
Any help would be great. Thanks a lot.

try this:
1. put a copy of framework-res.apk in your sdk/tools folder (this can be taken from a copy of the rom that you have installed at the moment)
2. boot your phone like usual; when the bootscreen appears, enter this into a command window directed at your adb (SDK/tools is the tools folder in my adb):
Code:
cd/
cd SDK/tools
adb reboot recovery
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
this should put it into the correct folder and reboot the phone. give it a little time, whenever I flash a new FW-res it seems to take a little longer than when I have not to boot up. I have a desire, I am only presuming thats where it needs to go

Thank you very much for your answer.
Code:
adb reboot recovery
worked flawlessly when the boot animation was showing. Although it took quite a while until the device was recognized.
Now the Android dude with the exclamation mark is on the screen (recovery). Right now the device is not recognized. Therefore I cannot execute
Code:
adb remount
or any other adb commands.
This was one of my initial questions: how do I get to access the file-system from recovery?
Btw: is there any difference from manually (trackball + powerbutton) going to recovery to using adb?
Thanks

can you get into the green recovery screen by executing the .bat file after doing the reboot/recovery? I find sometimes it can take up to five tries to push the files correctly.
if you can do that, then you can execute the rest pretty easily.
you can even turn it into a 'mass storage device' to put an update.zip on the sdcard
edit: this one was the recovery I was meaning.
the other way to get into that is
Code:
How to boot in Recovery Mode
Boot the phone while holding down the VOLUMEDOWN-key.
Navigate to RECOVERY with the the VOLUMEDOWN-key.
Press the POWER-key to select.
anything other than the information above and I can't be much use, this is about as far as my adb and android knowledge extends sorry.
GL

yes, I do get the recovery screen but I cannot execute adb commands from there. Any hints?

Well, if you can't access terminal (console) from recovery, try fastboot, and reflash the whole firmware WITHOUT wiping. That should do the trick!

Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?

wouldnt hurt. my next suggestion would then be an untouched rom (maybe 2.1 so you dont have a problem with the bootloader changing versions)

wouldn't fastboot allow me to copy the file to the system? I found this command for fastboot:
Code:
flash <partition> [ <filename> ] write a file to a flash partition
I think I will just have to flash the system-image:
Code:
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
Taken from http://forum.xda-developers.com/showthread.php?t=619153
Correct?
Then I need to find a system.img

Sorry for this double-post but I guess you guys don't come back, otherwise...
Can anyone provide a system.img for me? I've just tried the one from the stock PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip but received
Code:
sending 'system' (116663 KB)... OKAY
writing 'system'... INFOs
FAILED (remote: signature verify fail)
Edit: I have a LOCKED bootloader

can you either try using a stock rom rather than a cooked one, or try resigning the rom you are trying to flash?
Sent from my HTC Desire using XDA App

I have also accidentally deleted my framework-res.apk, and my X10 won't boot (duh). Now When I use the command "adb remount", I get the error message: "remount failed: Operation not permitted". How do I push framework-res.apk to my phone now?

I thought I was using a stock rom with
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip
update-nexusone-FRF91-stock-noradio-signed.zip
How does resigning work? I guess there are tools for this. Never used a cooked rom so far.

signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.

nzdcoy said:
signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.
Click to expand...
Click to collapse
Okay, signing worked for the zip file. But the system.img is still not working.
What do you mean with adb? What should I do? I guess the problem is that the system is not fully booted and I don't get root at that stage.

which rom have you tried to flash in FASTBOOT? I would expect PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip to work since it is a stock rom, but the other one looks like it has been repackaged.
knox420 said:
Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?
Click to expand...
Click to collapse
can you try doing this with the PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip one?
if possible try doing it without resigning the zip first.

Alright, none of this worked. I tried it all but in the end I had to realize I lack too much knowledge.
I wiped everything and reinstalled Cyanogen Mod 6 RC3. System's up and running.
Thanks for any help, though.

Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Click to expand...
Click to collapse
You mean get the card out of the phone and plug into a card reader?

cryshop said:
You mean get the card out of the phone and plug into a card reader?
Click to expand...
Click to collapse
What I meant -back in the days- was that I wanted to access the card while still in the phone. From the bootloader. Now this is possible with ClockworkMod or AmonRa Recovery.
Thanks anyway

[Q] SBF Flash Error - FEBE 0047

So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.

strakajagr said:
So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.
Click to expand...
Click to collapse
Confirm that your SBF file is not corrupt. Try downloading it from a different source and check hashes

I have tried 3 sbf's thus far. 2 .330's (from different locations) and 1 .290. The error message is always the same. I'm not sure if it matters, but I have clockword mod installed on my phone as well as Fission.

I'm not sure if having Mods and roms who affect your phone. But just incase have you tried clearing the cache,data,partition from the recovery menu?

I have... again, no luck. It just appears that rsd lite flat out can't communicate with my phone even though it definitely SEES the phone when it's connected. For the life of me I can't figure out why. I found ONE thread on another site where someone posted the same error and reported the same problem. Someone linked him to a boiler plate SBF installation instruction page, which obviously I have tried unsuccessfully several times. It's killing me knowing that there is so much more performance in my phone that I just can't get. My original Droid outperformed this POS. UGH

That certainly is frustrating. The only thing I can think of is trying a different USB cable that is shielded or otherwise, or another computer/OS maybe it's causing a error. If you've already tried that with no results, all I can say is sorry man and keep trying.

I was just reading this thread: http://forum.xda-developers.com/showthread.php?t=1236781 where the final poster said there are a couple of bad .330 sbfs circulating the web, and that the best way around it was to try to sbf a .29 and then ipdate from there.
BTW, op, I agree. My droid one can kick my D2G's ass blindfolded.
Good luck,
Dan

Hi mate, i have had this issue before, please try this as this is the way around my issue =
follow this link and download the rar file (http://www.multiupload.com/FIW8B8TJ7I), flash this file (using rdslite 4.9 , Make sure it is rds lite 4.9!) = http://www.mediafire.com/file/9c6u55c26e1h9y1/RSD Lite 4.9.rar
Being on clock work etc... wont make a differnce but to put your phone in boot loader mode, please do it this way and not the other loaders way.
turn off the phone, press and hold the up and down volume buttons together (make sure you are pressing and holding them down together keep them hold down and dont let go) press the power button while still holding the volume buttons and wait till bootloader comes and then let go, onces it says it in there
Launch RSDLite (make sure device appears in window)
Select SBF (doesnt matter where the file is, just point it to the right place)
click start.
Once it gets to 100% , pull it out and restart the phone (it should reboot it normally but I find it doesn't always do it) so either unplug and let it reboot or pull the battery out and reboot, fingers crossed it will boot in to stock and then you can upgrade from there.

"No such file or directory" help!
Hello,
I am having issues following these instructions as a part of the instructions from
droidforums' root-droid-1-regardless-os-version
after running this:
chmod +x sbf_flash
Then running
sudo ./sbf_flash update.zip
I get the following:
[email protected] ~ $ sudo ./sbf_flash update.zip
[sudo] password for gjohnhazel:
SBF FLASH 1.24 (mbm)
opticaldelusion
update.zip: No such file or directory
Usage: sbf_flash <filename>
My Droid is plugged in, with update.zip in the root of the SD Card and Bootloader 2C.7C with Transfer Mode set to USB.
Can anyone help?
Note: Where it says "opticaldelusion" it's actually the link, but I'm not allowed to have hyperlinks in this message.

sbf_flash is used to load an SBF image (which should be stored on your PC for sbf_flash to access it) into your phone.
It's not a tool to flash OTA/normal update packages.
To flash a normal update.zip you need to use either stock (for stock firmware updates) or ClockworkMod Recovery (for custom ROMs).

[Q] Velocity CRUZ T103 (PT701) bricked

Oh I am hoping someone here can help me out here. I just got this tablet, and tried to do the Froyo update, only to find out (too late) that this model is different and not up-gradable to the 2.2. After screwing around a bit with it, not sure what happened, but now the entire system is gone.
It boots to the Cruz logo, and sits there. ADB recognizes it, but I have no shell access, and when I do a ADB ls /system it lists only 2 files, with random numbers.
ADB remount - FAILS
ADB reboot fastboot - FAILS (just reboots it)
ADB reboot recovery - gets to recovery (in ADB devices) but tablet is blank, but no sh access
Vol + & power do nothing.
Vol - & power do nothing
While attached to my PC (Win7-64) and hit the reset and Vol -, it shows up as JZ4760 USB Boot, but Windows REFUSES to let me install any drivers for it. (Got the USBToolKit, but even after turning off driver signing, it still says they're not signed and refuses to load them)
I got the 2.0 firmware (default) so now what I need it a way to push the img files to the tab (hopefully)
Any ideas, or is this thing really a neat little brick now?
Thanks

No one?? Come on guys...I've been on this site for a long time, and have seen some of you pull out a brick and make a phone out of it again. LOL
I'm thinking if I can just get fastboot to load somehow on the tablet, I could issue commands from my PC to "push" the image files back over.
Question is: how do I get fastboot to get onto the tablet to load into???

I would like a copy of your firmware if still available for the cruz of course impossible to find as site is no longer hosted

delete don't work

Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!

I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...

C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.

C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk

I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.

You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work