Related
I know this is possible depending on the phone, but on the Vibrant I have not found a way to install clockwork mod without using USB. I saw that mobile odin was an option for some samsung phones but not the Vibrant.
My usb port is dead, no warranty etc. I bought it for 70 in like new condition with knowledge that the port was bad. I figured that the port needed to be soldered back down. But after taking the phone apart, I don't see anything wrong with it. Its not loose on the board, but the socket itself is loose inside.
The baseband is KA2 Eclair. I got it rooted with the oneclickroot tool.
On a side note, the phone also came with pictures of the seller and all his girlfriends naked . Not pretty
So let me review what you want to do, you want to install CWR without having a USB port. Seems easy enough.
Firstly, find a app that will let you connect to your phone to your computer, apps like Dropbox, Box, and this app i put up on these forums a bit ago will do more than just the job HERE
install one of those, which ever you like. I'll use the MIUI File Manager as a example throughout this post because its the easiest.
Open the app, go to the FTP and start service, go to your computer open MY COMPUTER and type in ftp://all your #'s
Put this file in your ROOT meaning just in sdcard/ no folders just drag and drop it in there. DO NOT RENAME,EXTRACT OR ANYTHING TO THE .ZIP just put it in the sdcard/
*Thanks for the CWR file from Woodrube and S15*
Now go into Recovery mode on your phone
Power + Volume up and down ( i think )
Press REINSTALL PACKAGES
It SHOULD say something like booting into clockwork recovery.
it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there.
Just reply if i'm explaining something wrong or if you need more help.
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
djquick said:
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
Click to expand...
Click to collapse
To each his own, Rom Manager never has worked great on my phone. Even bricked it completely once and I don't believe it was user error.
Relevant guide, +1 cookie. One suggestion though, organize the steps a bit further so there is a clear distinction between steps.
ie:
• Now go into Recovery mode on your phone, Power + Volume up and down ( i think )
• Press REINSTALL PACKAGES. It SHOULD say something like booting into clockwork recovery. it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there."
Anywho, to the OP: Since it's rooted, why aren't you simply downloading ROM Manager from the market and installing CWR from there?
edit/ beaten
Don't get me wrong, your tutorial is spot on, I just never had any problems with ROM manager before so I threw it out as a suggestion.
Sent from my Nexus S using xda premium
working on it now, big thanks!
TheEnternal said:
working on it now, big thanks!
Click to expand...
Click to collapse
As far as the port goes, Eugene, Krylon360 and myself all fried ours when we were porting the V4G - so you may not visibly see anything wrong with it at all.
Thanks guys, I ended up semi bricking the phone . Even though it was my 6th droid device. Not sure what I did, I was in recovery and everything was working, then went to reboot and it was stuck on the Galaxy screen, could no longer get into recovery. Too bad that USB port was out . I ended up just reselling it to a guy for parts and still made some profit off it. Shame though, that AMOLED display was beautiful. Ended up getting a G2X yesterday for 195, just missed one at 150 on craigslist. Already got it up with CM 7.2 with a minor OC. Hopefully towards then end of this year I might be able to get a Galaxy 2 for cheap.
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
johnson8cyl said:
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
i have tried this.
but gingerbread loader and froyo loader are different.
it gave an error at flashing and stopped flashing.
Hmmm. That would require fastboot huh. Don't know of a wireless way to use that. Is there an unroot procedure you could do from your sdcard without a cord and then re-root to gb perhaps?
Sent from my HTC Sensation 4G using XDA
and i'm asking for something like this.
but i ask for froyo not unroot.
to flash from sd card.
it gives an error
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5
it was necessary to remove it when upgrading to the clockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and updare-binary) to create working update zip packages.
installation aborted.
I don't think it is possible to downgrade to froyo from CM7 without ODIN. I might be wrong but that is how i remember it.
Though i did find this thread..
http://forum.xda-developers.com/showthread.php?t=1149158
But i don't know how that worked for people. You might wanna research a little bit more. IMO you are better off going to ICS.
Br1cK'd said:
Just use Odin, don't shortcut it. The OP here has a very very basic idea of the reason and necessity to change these files, and has not provided a complete set of steps in two different "guides" he has posted here, and nobody has been successful as per the reports.
Bottom line, save both yourself and dev in the future a headache, and just use Odin.
Click to expand...
Click to collapse
its very sad ((((
Just a reminder to some who have USB port problems. I'm not trying to insult anyone's intelligence here but remember Samsung phones are picky about USB cables.
I know because my phone was Semi bricked while doing Odin. Turned out my original Samsung cable went bad halfway through Odin'ing a new bootloader. After two months of playing with it I tried literally 5 different data cables that all fully worked for other phones and a few cheap off the street cables. Some would not even charge my vibrant but would work fine for data and charge on my wife's LG Quantum. Hard to find good micro-USB cables here in Peru. Finally I ended up modifying my original cable with another cable's micro-usb connector and wrapping a separate ground wire around the shield to get it to work. Samsung phones must require really good shielding to communicate and possibly not all cables have the shield connected on both sides or are properly shielded.
zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Check out 'mobileODIN' on the market.
Plot: I have a Nexus 4 with a broken nand memory, I bought a £32 nexus 4 16gb from eBay with a broken glass and broken digitizer, I replaced the motherboards and voila, I have a working Nexus 4 and a device with a broken digitizer that won't go pass boot.
So, my "broken" nexus 4 doesn't have a working touchscreen, nor a NAND memory, but what it has 2GB of RAM and a nice processor it's the ability to boot an image with Fastboot, eg: I've booted stuff like Clockworkmod Touch Recovery or TWRP Touch Recovery.
What I would love to do is to boot a Linux version on my broken nexus and use it as a web server, or other stuff like ... display my CCTV cameras, since the display still works...
I tried multiple ARM variants, and the closest I got was with distro.ibiblio.org/tinycorelinux/4.x/armv6/piCore.gz . It was the only image small enough to download via fastboot, but... it's stuck at booting, probably I need to do smt else for it.
Has anybody got any tips for me? Anybody tried it before?
My plan would be:
1. Boot successfully any linux kernel
2. Buy an OTG Y cable to connect an external HDD.
3. Create a linux image that would boot from that external HDD
4. Control my new "linux server" via SSH
Hope this post will get some attention, I think it could be a nice thing for old unused phones as well as phones with broken displays that nobody took the time to repair.
tcr92 said:
Plot: I have a Nexus 4 with a broken nand memory, I bought a £32 nexus 4 16gb from eBay with a broken glass and broken digitizer, I replaced the motherboards and voila, I have a working Nexus 4 and a device with a broken digitizer that won't go pass boot.
So, my "broken" nexus 4 doesn't have a working touchscreen, nor a NAND memory, but what it has 2GB of RAM and a nice processor it's the ability to boot an image with Fastboot, eg: I've booted stuff like Clockworkmod Touch Recovery or TWRP Touch Recovery.
What I would love to do is to boot a Linux version on my broken nexus and use it as a web server, or other stuff like ... display my CCTV cameras, since the display still works...
I tried multiple ARM variants, and the closest I got was with distro.ibiblio.org/tinycorelinux/4.x/armv6/piCore.gz . It was the only image small enough to download via fastboot, but... it's stuck at booting, probably I need to do smt else for it.
Has anybody got any tips for me? Anybody tried it before?
My plan would be:
1. Boot successfully any linux kernel
2. Buy an OTG Y cable to connect an external HDD.
3. Create a linux image that would boot from that external HDD
4. Control my new "linux server" via SSH
Hope this post will get some attention, I think it could be a nice thing for old unused phones as well as phones with broken displays that nobody took the time to repair.
Click to expand...
Click to collapse
Sounds like an interesting project, but why not you just replace the phone? Google will accept your phone (even if you didn't buy it from them) in almost any condition and give you a replacement if you call them (85583NEXUS is the number)
If you are really interested, I was able to get a 3.6 kernel running on my galaxy nexus about a year ago by building it myself. Any prebuilt images will surely not work. Even though I got the kernel running, it was basically worthless as I did not have any mechanisms of controlling it, you could try configuring it to boot from your hard drive to get an SSH session running.
How come you didn't go through warranty for the initial NAND issue?
That said, you might be able to modify a ramdisk to point your partitions to those on a usb disk (of course with an otg capable kernel). Or perhaps you could look into multirom/kexec hardboot, and be reliant on the initial fastboot boot just to kick that into action. Multirom bases off twrp though, so that'd be hard to execute without a working digitizer. If anything, you could branch off that idea (if you can't manage to directly tweak your ramdisk to mount everything off a usbdisk)..
If anything, see if it's google would replace the phone for the bad nand. Swap the board back.. Then you'd end up with "just" a back digitizer and be in a much better position.
ziddey said:
How come you didn't go through warranty for the initial NAND issue?
That said, you might be able to modify a ramdisk to point your partitions to those on a usb disk (of course with an otg capable kernel). Or perhaps you could look into multirom/kexec hardboot, and be reliant on the initial fastboot boot just to kick that into action. Multirom bases off twrp though, so that'd be hard to execute without a working digitizer. If anything, you could branch off that idea (if you can't manage to directly tweak your ramdisk to mount everything off a usbdisk)..
If anything, see if it's google would replace the phone for the bad nand. Swap the board back.. Then you'd end up with "just" a back digitizer and be in a much better position.
Click to expand...
Click to collapse
I don't think google would have accepted it because:
- NAND Memory failed 99% because I flashed Franco Kernel's nightly version every... night.
- Obviously the phone's bootloader was unlocked and for some reason I haven't managed to lock it
- The back was cracked
I guess I can use my working version to play around with the kernel till it does what I want, I'll look into multirom/kexec. Any idea where can I get a good OTG Y-Cable. I've seen some, but I want to go for one proven to work well.
Bleh, there are times when I'm testing some code and end up flashing boot 100 times a day.
ziddey said:
Bleh, there are times when I'm testing some code and end up flashing boot 100 times a day.
Click to expand...
Click to collapse
Yeah, me flashing may not be the reason, however, my phone had the back cracked and a bit of the middle line damaged, so I bet nobody would have fixed it on warranty. I got really cheap and fast getting a replacement on ebay with a broken screen and do the swap, I posted two images below to show that the nand was really just... write only (is).
i.imgur.com/2VrVw6U.png - Via LG's Own Recovery Software (I know the DLL is wrong, but it's supposed to work) // i.imgur.com/SJDmTk9.png (Via Fastboot)
Sorry for not being able to post images, still have to go up to 10 posts. I've been quite selfish so far and only got info from XDA, promise if I will get anywhere with this threat I'll make a tutorial of how to do it and an example of a useful thing you can do with a broken phone .
==============
Anw, back on the subject, can anybody help me with how to install MultiBoot on a USB Stick? I would assume the things will go as follows: Have some magic on the USB stick, have a boot image that boots from there (via FASTBOOT) ==> multiboot boots my desired OS from the USB stick as well.
not sure what you're doing there for the second picture. Looks like some sort of script..
first pic looks fine. It's supposed to only get to 85%.
As for multirom, it's on you to learn how to create a ramdisk->boot.img that will mount usb partitions instead of mmcblock.
ziddey said:
not sure what you're doing there for the second picture. Looks like some sort of script..
first pic looks fine. It's supposed to only get to 85%.
As for multirom, it's on you to learn how to create a ramdisk->boot.img that will mount usb partitions instead of mmcblock.
Click to expand...
Click to collapse
It's supposed to get to 85% and restart. However it does not, I restarted it manually into bootloader, and tried to use flash-all.bat from the flashfactory for my model.. and then I get all of those write errors (as before) (that was a try to flash a custom recovery with Nexus Toolkit, I tried it manually). As a note, erasing all the partition works, formatting emmc partition obviously doesn't, formatting ext4 partitions: starts creating the filesystem, the partition is sent and then ... BOOM failed flash write failure as when I am trying to flash anything else.
As for the ramdisk and all, I shall use my medium Linux experience to dig into that and I'll let you guys know if I will get anywhere. For now I'm doing my best to make my own Y Cable ... this will be tricky.
Thanks to all of you who support my post, it's really cool to find a place where I can talk about stuff like this. I really hope if I manage to get somewhere I will make a tutorial that will help someone to put their old/bricked phones to good use.
Okay I'm having another stab at repairing my device, because it CANT be broken, it broke from an OTA update to 4.4, but i've used the restore back to 4.3 from Advent but still nothing, I have tried a few things, it gets stuck at the TEGRA Note logo so it has to be something with the boot, I did notice in CWM it couldn't mound the data partition but i fixed that by flashing userdata from fastboot, still got the stuck on boot issue, I'm trying a zip of a 4.4 rom, then i'll try it, if it doesn't work I'm gonna try a 4.3 boot img but i don't know if that will help. Any ideas?
Can you get it into APX?
Andy4Shurr said:
Can you get it into APX?
Click to expand...
Click to collapse
Yes which I used to do the Advent apx restore. That was the first ever thing I tried after the OTA failed, you'd expect it to fix it since I had 0 root, 0 custom rom or anything, it was an official OTA that broke my device but the advent apx did not solve it.
LightInDark said:
Yes which I used to do the Advent apx restore. That was the first ever thing I tried after the OTA failed, you'd expect it to fix it since I had 0 root, 0 custom rom or anything, it was an official OTA that broke my device but the advent apx did not solve it.
Click to expand...
Click to collapse
Did the transfer seem to go ok, were there any messages? I only ask because I had a problem where in APX and flashing back to 4.4 using Super Tools it gave me an error right at the end and kept getting stuck at the boot logo. Another time it would flash ok but system processes kept crashing etc on boot.
I found out that using a different usb port on my laptop solved all the problems, I haven't had any trouble since doing that. I don't know why or if it will help your case to do this but maybe give the nvflash another try using a different USB port and see if it makes any difference!
Andy4Shurr said:
Did the transfer seem to go ok, were there any messages? I only ask because I had a problem where in APX and flashing back to 4.4 using Super Tools it gave me an error right at the end and kept getting stuck at the boot logo. Another time it would flash ok but system processes kept crashing etc on boot.
I found out that using a different usb port on my laptop solved all the problems, I haven't had any trouble since doing that. I don't know why or if it will help your case to do this but maybe give the nvflash another try using a different USB port and see if it makes any difference!
Click to expand...
Click to collapse
I've tried both the super tool 4.4 flash and APX multiple times, the super tool just gives an error and doesnt flash system, boot or recovery images. APX doesn't seem to give any errors. Tried on both the USB 3 ports and USB 2 ports and with 2 cables, the official one and the cable for my LG G2.
What you will need:
KingRoot V4.5.0.901 (latest version as of this posting)
Rooting your phone will void your warranty.
Terminal Emulator for Android
Replace KingUser with SuperSU
MtkDroidTools v2.5.3-updated
adbd Insecure v2.00
SP Flash Tool
I am not going to get into how to install ADB drivers, MtkDroidTools, or SP Flash Tool. If you are not experienced with rooting, flashing, etc., please do some research.
Okay, let's get started
First you will need to get your phone rooted. Download KingRoot using the link above and follow this guide.
Next you will need to replace KingUser with SuperSU.
Now that we have the phone rooted and SuperSU in place, we can use MtkDroidTools to make a backup of the phone.
This video will show you how to backup your phone with MtkDroidTools (make sure you have downloaded the version I provided, as this has updated ADB files). Also make sure you enabled adbd Insecure before you connect your phone (you don't need to check enable at boot).
Once you have a successful backup, you need to create the files for flashing (scroll down to PREPARING EXTRACTED MTK ANDROID FLASH FILES FOR FLASH TOOLS) if you need to flash back to the original firmware.
Hopefully you now have a backup of your phone. Now we can install a custom recovery. You can use either TWRP (rename to recovery.img) or PhilZ.
The easiest way to flash the custom recovery is with SP Flash Tool. Connect your phone (you don't need adbd Insecure enabled for this). Run flash_tool.exe as administrator. For scatter-loading File click on the Scatter-loading folder
and navigate to your MtkDroidTools backups folder. There should be a folder that starts with BLU-STUDIO-C. Open that folder and select MT6582_Android_scatter.txt. For the recovery file, navigate to the one you downloaded (TWRP or PhilZ) by clicking on the Location column next to RECOVERY.
Make sure RECOVERY is the only box checked before proceeding. Now you have your scatter file and custom recovery loaded. Click on the Download button. Nothing will happen at this point. Now shut down your phone (not restart). Once your phone shuts down completely, plug it in via USB and you should see it begin to flash the custom recovery. If not, then you need to make sure you have the necessary drivers installed. Once it's complete, you can close out SP Flash Tool and disconnect your phone. After your phone is disconnected, hold down the power and volume up buttons until the recovery menu appears :good:
Post your feedback, and if you encounter any problems, please be as descriptive as possible. Good Luck
Credits:
@AlexZap who was the first to help me along this crazy journey
@yuweng for all his help in backing up the phone and for PhilZ recovery
@bigrammy for porting TWRP Recovery
@rua1 for MtkDroidTools
@carliv for CarlivTouchRecovery
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
cteeto said:
Thanks for this guide, it has worked for me so far (backing up with mtkdroidtools now). Can I ask, why is it neccessary to use SPFT to flash the recovery? I have used fastboot to flash the recovery without issues. I just
$ fastboot oem unlock
and then was able to
$ fastboot flash recovery recovery.img
and it worked.
html
Also, would you be able to port some custom roms for this phone?
Click to expand...
Click to collapse
Glad it worked out for you. Yes, fastboot is also an option (as you all ready know).
Recovery could probably be flashed with Flashify, but haven't tried it. I am not a developer, so no I can't port any ROM's, and take no credit for the custom recoveries listed here.
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
sandix said:
If someone can post Cyanogenmod for a phone that uses the same hardware, I can port that for this phone.
Click to expand...
Click to collapse
ABSOLUTLY.......this would just be AMAZING...if anyone could manage to make a Cyanogenmod for this phone.....:good:
Bricked Blu Studio C (D830U)
Hey,
Was wondering if you could help me out here, as I'm a TOTAL Noob when it Comes to BLU phones But not to flashing....
I've Bricked by Phone, The Computer and SP Flash Tools still recognize the phone..
I've Downloaded the proper ROM from NeedRom.com....
My Issues:
1. Can you Verify WHICH Driver I should Be Using for a FULL either Erase/Download Or a Firmware Upgrade (Not Sure Which)
2. I need a Scatter File the Contains ALL the Memory address and Supplies ALL the Check Marks for a FULL Rewrite Flash....The One with the rom is missing Preloader Android, Cache, and usrdata...
When I did JUST the Scatter file flash attempt I got the BROM_ERROR : S_DL_GET_DRAM_SETTING_FAIL ( 5054 )
I googled that and it said the Perloader wsn't right So I added the Perloader (And checked the "firmware.info file" and seen the Memory:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
So I tried Anyway and got the same error except this time it's 4032.
So Basically Can you tell Me Which Files In the ROM I Download Go Into Which SLOTS on SPFTools, and Which memory address' are correct the firmware file or the Scatter??
I really don't want to keep slamming the phone with "STUFF" and REALLY screw something up, I think I'm lucky it's even being recognized at this point....
Also the MTK_Allinone_DA.bin that comes with SPFTools is the right one??!?!
I'm Using Version 5.13.52.200
I'm Assuming Just a FULL Scatter file would solve the problem?!?!?
ANYHELP In this Would be VERY much Appreciated....
Thanks
Mike
EDIT:
Ok, I got it to 4001 Error, And it's saying that error is it's not connecting with the preloader, So I'm thinking (hoping) if I can get those 3 files, even if the cache is empty as long as the memory address is right, and the scatter.txt, and do a Firmware upgrade, Hope, will solve the problem, if not, On to Test Pins...
@bobl61
Could work together to enhance MTKDroid liek as
Increae number of CPU recognize by it (ex. MT67xx - just recognize it - not work with it)
Update the apk included and sued by MTKDroid (like MobileUncle/Root Explorer/SuperSU)
Upload the ROM or the link I think I know what's the problem @Miker1029
Fixed from the dead!
Swaelae113 said:
Upload the ROM or the link I think I know what's the problem @Miker1029
Click to expand...
Click to collapse
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
IMEI Problem
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
Update, Just a Heads Up I'm Assuming from Googling around, that Installing the NVRAM will wipe your IMEI, Still working on this aspect, But it doesn't seem to be Hindering the phone in anyway, As I said It Took along time to boot up, So I'm not sure if Re-writing the NVRAM made it work or not, I do know I formatted + Download, and It Sat On the Splash Screen, I shut down and Flashed just the NVRAM file, and It booted.....
NOW Should I go for a Custom Recovery??? LOL.... I'll wait.... But now that I know I can Fix it......Hmmmmm
Mike
Miker1029 said:
Hey Thanks, I've made some progress today, The rom is on Need Rom.com so best to just google Needrom and D830U as It's internal search doesn't work so well....
I Got a New (Cheap, Used Phone) and to my Suprise It's an MT65XX Chip set Also (ACK!!!!!)..................... NO WAY IT JUST BOOTED UP!!!!!!!!!!!!!!!!!!!!!!!!!!! TOOK FOREVER!!!!!
Ok I learned that with the Downloaded ROM from Needrom, You Need to Go to MTK Tools and Process blocks for flash, The go to the Directory you Extracted the ROM to, And It'll bring up the MD5 file click it and It'll create the Scatterfile and the "!FLASH" Directory, Then Navigate to the !FLASH (something) Directory and you'll have your scatterfile.txt, Load it up, I added ALL files (see Screen Shot) and it's booted up.... You need to use Preloader Drivers for it, And I HAD TO FORMAT AND FLASH.... And what you see in the SPFlashtool screen shot is what I flashed....
I'm not a GUIDE writer sorry, But Hopefully this will give hope to those like me (that have been bricked for ALONG TIME) Hope.....
If anyone needs info on this Ask, I'll try and answer.....
Mike
Click to expand...
Click to collapse
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
bobl61 said:
You are correct. I didn't realize the video on how to backup the stock rom did not include the next step which is to create the files needed to flash with MTK. Good catch, Miker1029 :good:
Click to expand...
Click to collapse
Hey Thanks, Maybe you can redo it or whatever, I was bricked for Months (Mainly Because i didn't know the Phone Type), Check out the screenshots to see the extent I went to Googling My Butt Off trying to figure it out, But once I did, All went good, I've flashed Atleast 100 Phones, For me, Friends, Family, Never had the Kind of issues I had with the MTK Chipset...
But now that I have it, It's rooted, Flashed, Xposed Framework Installed and working, Exactly what I was "Originally" trying to do....LOL, It's good now tho...
Now Funny thing I lost My Compass on it, and Sensor detector says it's working fine, So Not sure what's Interfering With it.... Hate to Re-Flash
SOOO, If I GOTTA re-flash Been looking around for 6.0 (Marshmallow) Build for it (No Luck)
1st Pic, Just the Face.
2nd Pic, Where I Cut the Battery Connector (Casing) to the Board so I could Disconnect the Battery without taking the phone apart....
3rd Pic, I left the screws out as There's a Little spring on the Bottom-Left (Looking from the back) that Makes the speaker work, And On the Bottom-Right is the antenna connection that I can't get to "Snap" back in..... So I left the screws out to fix those minor issues, I'm trying to NOT open it anymore then I already have LOL
Mike
I want custom ROM for blu studio c 5+5
[Q
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
bertucci25 said:
So i did this exactly as its written and now my d830u its freezing in blu logo... and im not able to enter recovery img, i used the philz link since the other one is deleted... hope any1 could help!
Click to expand...
Click to collapse
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Miker1029 said:
Little. More details would be nice..
Did you download the rom from needrom?
Did you create the flashable files from that rom?
Did you generate and add scatter file?
Did you format and flash?
Did you check device manager to see if it's using the pre drives?
Did you remove any and alll USB / MTK drives, except the pre driver?
Disd you start the flash THEN plug on the phone? Does MTK say on the bottom PRE driver?
And finally i believe my issue was some kind of lock up as the battery isnt removable so i cut the casing to access the battery connector and basically stated the flash and attached the battery connection..
Alls i can say is i was at the exact same spot as you i flashed 3 or 4 totally incorrect roms, and had that driver issue, when i finally got the proper rom and fixed the driver issue it worked, and it did take like 20 to 30 minutes for the ohone to boot the 1st time..
Mike
---------- Post added at 11:05 AM ---------- Previous post was at 10:33 AM ----------
Also, i used the recovery that came with the rom and when it finally booted up, i flashed the custom recovery...
And if you decide to go with disconnecting the battery be careful as some months after the female connection on the board broke completely off... I hate any phone without a way to break the electrical connection think it's stupid..
Good luck,
Mike
Click to expand...
Click to collapse
Ok i'm going to explain my journey from soft-to-revive history:
I was trying to install a custom recovery for my D830U (Blu) and end up in this thread. I made all the steps
-Rooted the phone with kingroot
-Removed kingroot and installed SuperSU
-Instaled insecure adbd insecure
-I made a backup of my stock rom with MtkDroidsTool(wich is the needrom provided, since i flashed my phone while ago)
-Drivers are installed (VCOM)
Everything is downloaded from the links in the post
Ok at this point i did everything exactly like the guide, great
Ok now the part were "something" failed is:
I got the scatter file in the mtkdroidstool backup folder and REPLACED the recovery to the PhilZ recovery.img in the link of the first post. And flashed normaly. Here is where things got bad
I disconnected the phone and realized it got bootloop, couldnt start the phone and can't get into recovery (when i press vol+ button it goes to black screen), because i installed a bad/not compatible philz recovery.img(AGAIN ITS FROM THE PROVIDED LINK) ok now i'm worried but no problem, i tried to reflash with original stock rom and eventually after many tries i got into a normal recovery mode and the phone boots normal..
Now my phone is at the start point. Can you tell me which version of custom recovery are you currently using? Or what procedure should i follow to get into it? Again thanks! Cheers.
Ya I'll upload the recovery i used, I'll get it here sometime today..
I'm not sure which it is, as i said, the power connection for the battery broke off the board awhile ago, so it's either philz or twrp.
Also, if I'm remembering correctly, you have to add the other drivers, not the pre driver, you can try it with the pre, and if you don't get the green check use the other ones, and when you go flash, I'd backup your recovery you have now and put it somewhere safe...
Ill also add the version of xposed i used, if i can find it.. I know i had to install the. Zip files from recovery...
Mike
I believe this is the custom recovery i flashed, i no longer have the phone to test, but i believe i removed all except the stock and custom..
As i said back up your current recovery..
Let me know so i can mark it my puter.. Thanks
Mike
Also let me add, I had a bad philz also, not sure if i got it here, or somewhere else, but i have it marked as philz doesnt work on my computer...
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Miker1029 said:
Ok folks, two downloads, can you provide an update?
I'm trying to help with an obscure phone..
So a report back, for the people, would be nice.
Mike
Click to expand...
Click to collapse
Hey mike im going to test this today i'll update my progress in a few! wish me good luck :silly:
Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service